amake

The AWS CLI has --[no]-dry-run in many of its subcommands.

https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-h...

Yeah and there's already a well-known (at least I already knew about it and have been using it for a while) package started in 2022 called "copilot" for Emacs that is actually a client for GitHub Copilot: https://github.com/zerolfx/copilot.el

Given the lack of namespacing in Elisp (or, rather, the informal namespacing conventions by which these two packages collide) it's unfortunate that this package chose the same name.

Ah, that does look to be the case. I didn't know about that one.

    Signature
    (letrec BINDERS &rest BODY)
    
    Documentation
    Bind variables according to BINDERS then eval BODY.
    
    The value of the last form in BODY is returned.
    Each element of BINDERS is a list (SYMBOL VALUEFORM) that binds
    SYMBOL to the value of VALUEFORM.
    
    The main difference between this macro and let/let* is that
    all symbols are bound before any of the VALUEFORMs are evalled.

Anyway, as far as I'm seeing it's perfectly possible to implement let* consistent with the above behavior as a macro without mutation as such:

    (define-macro (let* bindings &rest body)
      (if (null? bindings)
        `(progn ,@body)
        `(let (,(car bindings))
           (let* ,(cdr bindings)
             ,@body))))

> let* permits expressions on the right refer to arbitrary other symbols bound by the let*

In what language? I just checked Elisp, SBCL, and Guile, and they all error out if you refer to a variable not previously defined by a left-to-right traversal of the varlist:

    (let* ((a (+ b 1)) (b 1)) a)

Edit: This doesn't work either:

    (let* ((a (lambda () (+ b 1))) (b 1)) (funcall a)) ; (funcall a) -> (a) for Schemes

Why does `let*` need to have mutation? It can be nested `let`s.

It's not just styling. The content is actually a `git format-patch` patch for the former a unified-format diff for the latter.

No one cares. Just don't use them.

No. People like them. No one is forcing you to use them. Stop complaining about it.

I agree entirely. PragmataPro is my daily driver, and anything else feels way too expansive.

Default Iosevka is close, but the leading is much larger. Luckily you can customize it to be almost identical (set `leading = 1110` in the config; value obtained by trial and error).

No need for the hat. As I understand, that is an explicit goal of influential political operatives like Grover Norquist and the Americans for Tax Reform (https://en.wikipedia.org/wiki/Americans_for_Tax_Reform)

The default iOS Japanese keyboard allows easily entering circled numerals and many other “exotic” characters.

MacPorts has provided binaries for many years at this point.

"Oh, a post about a programming font; let's see if there are any comments not from killjoys who can't help but advertise their hatred of ligatures"

*opens comments*

*shakes head, closes tab*

Heavy Emacs users may appreciate docker.el, which does a lot of the same things inside Emacs

https://github.com/Silex/docker.el

I suppose it was too late to ban lead from gasoline because everyone alive at the time had already been exposed.

> The team had several people in every time zone

Kind of hard to believe

Did you not read the article?

It's ambiguous because it's not clear what elements go into separate cells of the array.

Tell me you've never actually used programming ligatures without telling me etc. etc.

I would probably be considered an Emacs power user: I have used it for years as my daily driver for professional programming in many languages; I have an extensive custom config; I have published several non-trivial packages.

But I still had no idea that zones existed until today.

There are occasionally ads disguised as alerts, such as when you're running low on storage space it will suggest that you buy a paid tier of iCloud storage.

I think I have seen other ad-adjacent messaging for other paid Apple services but I can't think of any off the top of my head right now.

What does “aesthetic” mean to you in this context?

Oh boy time for this again:

> To all the people complaining about how they don't like ligatures:

> Nobody cares. If you don't like them, then don't use them. They are optional.

> Lots of people like them. Let people like things.

https://news.ycombinator.com/item?id=34589338

baka and boke are unrelated words.

The overlap is that the verb "bokeru" and its root "boke" can be used to describe someone losing their mental faculties e.g. through age or disease such as Alzheimer's, and by extension it can be used as an insult to mean "stupid" as well. But etymologically there is no connection.

Are you haranguing people about liking dark mode in comments sections as well, or just ligatures?

> It being good or better is science

Citation needed.

> It's not just personal preference, it's the science of usability

It's obviously personal preference, because many people prefer it. If I found ligatures harder to read or edit then I wouldn't use them, but I don't, so I do.

> programs with ligatures-by-default

Such as?

The ligatures discussed are implemented at the rendering level. The byte sequence of text is unchanged vs the "no ligature" scenario. So this has zero impact on screen readers.

To all the people complaining about how they don't like ligatures:

Nobody cares. If you don't like them, then don't use them. They are optional.

Lots of people like them. Let people like things.