Mahmoud Al-Qudsi

@erw7 Yes, this is under WSL, but they work even when SSH'd into Linux/macOS and running neovim there.

Neovim can possibly call `SetConsoleMode(..., GetConsoleMode(...) | ENABLE_VIRTUAL_TERMINAL_PROCESSING)` itself.

The code from nvim v0.8.0-dev+226-g07ade91f2 running under conhost.exe (not from Windows Terminal.app) under WSLv1 on Windows 10 1909 has the following mapping: * Ctrl-space: `` * Ctrl-2: `` * Ctrl-/:...

Note that there's a not-insignificant number of people that rejected the yarn 2.0 upgrade and have stuck to yarn 1.x because of the unnecessary churn, the break in npm compatibility,...

I agree — if I recall correctly, in my previous testing, an abruptly closed stdout fd generally does not result in a change to the exit code of core Unix...

Just a ping for those subscribed: @ridiculousfish committed some improvements to this as discussed in #5635

shift-delete matches the behavior of native Windows autocomplete inputs w/ history enabled, which was later adopted by Chrom(e|ium) and, I think, Firefox. I'm not comfortable with a plain delete binding,...

Treating that as an error would resolve my issues with it. It can still be always tokenized as a homedir expansion and it would resolve the ambiguity/non-deterministic behavior.

You are right and this is very unfortunate. As a first-party script, there's no reason why `dirs` should emit info in a way not natively ingestible by other fish scripts....

I'd be onboard with improving the current api surface for the directory stack, and agree it's unfortunate that there are too many separate commands to do everything. I feel like...