I think everyone says “couldn’t care less”. But Wiktionary does say “could care less” is “American, nonstandard, proscribed”, so I guess only Americans have that (defective) alternative phrase.
As programmers in programming culture, we have a distinction between hacker and, potentially, cracker that no ordinary person has. ESR’s prescriptivism is pretty much worthless in this respect: words mean what people think they mean and what people use them for, and programmers do not have a monopoly on how people use the term.
OED has the “computer intruder” sense first cited in 1963, and the “enthusiastic programmer” sense first in 1969 (“now much less common than sense 3a”). Cracker first appears in 1968.
Besides, it is easy to disambiguate which meaning people mean. “Hacker attack” can only refer to the common usage of the term, not programming-culture usage.
If you want ‘git diff | pager’ to work like that, you’re out of luck. There is no way for the pager to communicate with git or the shell to rerun the command; the pager doesn’t even know what program is on the writing side of its stdin pipe. You would need something like ‘pager --command "git diff"’, where the pager invokes a command producing output. I do agree that it would be nice.
To clarify, these aren’t the normal Feynman lectures. He lectured at a different institution and the author of this webpage transcribed those lectures to produce this set of notes. The content covered is different from the famous set of lectures.
iOS repeated “learns” new words that I use that are misspellings of real words (because I mistype things in a predictable way). It becomes so convinced that it will autocorrect the real word into the typo. And knowing how the keyboard works, I wouldn’t be surprised if it enlarges the touch targets for the typo once it thinks I meant to use the typo.
The cause is obvious: Apple is training on what I type, not what I send. Apple does not consider that I actually care about the accuracy of what I send and will fix errors; perhaps they optimize for people who are careless enough to send typoed messages, yet niche enough to commonly use words not in the default dictionary.
It is infuriating that I have ~50 manual corrections telling Apple to leave words alone and correct certain typos to the real words.
Strang does include that. I just checked the fourth edition, like you say you did. Scrolling down two pages to get to the first page of the table of contents, I see the heading “cosines and projections onto lines”. I navigate to that section and it explains all the logic, proof, and intuition behind the connection between angles and dot products. Please don’t spread misinformation…
> 'd/something' is doable with C-s something RET C-w
Doesn't this need to be C-s something C-r RET C-w? Because C-s positions the cursor at the end of the search match.
Give me M-q any day over gqap (or, if you're inside a multiline comment, 3gqq; or, if you're inside a multiline comment starting on the same line as code, just giving up).
Edit: though I have to admit that I'm missing 'dt.', 'd/something', etc.
OTOH, Neovim lets you edit the ex command line; e.g. '!}' might expand to ':.,.+5!', which lets you execute any other ex command simply by deleting the '!'. They both have advantages, and I'm certainly not advocating that forcing ex commands to work on lines is the best idea.
The Bourne shell certainly has problems, but IMHO fish should have stuck with POSIX syntax when it's "good enough" (TM). Stuff like $(code) vs (code) makes Fish feel like it just wants to be different.
Things I think are big problems:
* Needing to quote practically everything
* Needing to remember if/fi, case/esac, while/do/done, for/in/do/done, etc.