That's not an effect. As both in the case of a dividedend and a stock buy back, the company's market cap drops by the amount of cash that's being distributed out, creating an identical re-buying situation in market cap-weighted index funds. Stock price itself is irrelevant for index fund rebalances (unlike for shareholder returns).

> So for my definition of “everywhere,” with the caveats mentioned above, the following features work everywhere. YMMV.

  .
  ^, $
  […], [^…]
  \*
  \w, \W, \s, \S
  \1 - \9 backreferences
  \b \B
  ? + 
  | alternation
  {n,m} for counting matches
  (...) capturing

Except that these don't work in macOS/BSD sed (even with -E flag):

- \w, \W, \s, \S - need to use POSIX classes instead: [[:alnum:]], [^[:alnum:]], [[:space:]], [^[:space:]]

- \b - need to use use [[:<:]] (word start) and [[:>:]] (word end) instead

- \B - (not a word start/end) no alternatives

Easy with https://karabiner-elements.pqrs.org on Mac.

It's not documented, but unfortunately neither of these re-signs the commits even if GPG signing is configured. They are based on `git replay`, and that doesn't sign either (at least yet).

How/why did it consume more tokens?

Well, thing is I ask it doesn't things where sandbox fails.

And then it has to bypass sandbox to run those command with elevated permission.

This double tripe boosts token usage.

I don't think average developer workflow can be really limited to a workspace. You'll need commands which touch your system or require more privilege

I think the script would be named as `#` so that it can be called via `\# mycmd` instead of `\\# mycmd`.

Unless you disable cursor blinking because you find it annoying (like I do).

Yeah, disabling cursor blinking is the first configuration I do in any terminal.

Node 24+ does respect HTTP_PROXY when NODE_USE_ENV_PROXY=1 is set.

Node v22.21+ as well

> GitHub’s contributor graphs use mailmap.

This is not true, .mailmap is [unfortunately] not supported by GitHub: https://github.com/orgs/community/discussions/22518

Do you have an example of this in mind where the known "tit for tat" strategy falls short?

I don't have a concrete example, but I think you can invent plenty of iterated prisoner's dilemmas with whatever modified rules and variables and find 'tit-for-tat' isn't the end-all-be-all. Like it changes things if there's an infinite or an unknown number of rounds, some of the defects are 'noise', etc.,.