At the start of the game, qRook - king - kRook all store the location e1.
If the king moves (say we're playing the Bongcloud), qR and kR get set back to their original squares, a1 and h1. Now if the King slides back, castling is off the board.
I love reST and I think it lost primarily because of distribution. I.e., the people using it did not have large audiences and didn't put much effort into promoting it.
It's a shame because reST is almost as easy on the eyes as Markdown and is much more capable without being too much more complex.
Disclosure, I do work for Josh, and I can tell you that he's thought quite deeply about the negative implications of the agents that are coming. Among enumerating the ways in which AI agents will transform knowledge work, this points out the ways which we might come to regret.
> Even if this plays out over 20 or 30 years instead of 10 years, what kind of world are we leaving for our descendants?
> What should we be doing today to prepare for (or prevent) this future?
One thing I find myself wanting is an emacs-lite alternative to less/more. Something that would let me page though a file, but use my emacs bindings to search, filter, browse etc. I've already built up my muscle memory, so it would be great if I could reuse it for this purpose.
Thought I'd tag along to this submission and see if anyone has a recommendation?
`llm` gives my tool a standard bin to call to invoke completions, and configuring and managing it is the user's responsibility.
If more tools started expecting something like this, it could become a defacto standard. Then maybe the OS would begin to provide it.
reply