Qi Xiao

Revisiting this, I'm not convinced of the original proposal but I will change `!=`, `!=s` and `not-eq` to only accept two arguments.

Supporting this requires `take` to *stop* working for byte input and is thus a breaking change. Looking at the [search results](https://github.com/search?q=take+extension%3Aelv&type=Code&ref=advsearch&l=&l=), most of the code should be OK. An exception...

`take` does not know whether the first input will come from the value channel or the byte pipe, so it has to listen to both at the same time; this...

Modified function keys are not well supported across terminals. It's likely that the terminal is not sending anything at all, or it could be sending something that Elvish's key code...

Change the title to refer to the VS Code extension. The completion in the extension is actually driven by the same code behind CLI completion, but because `elvish -lsp` doesn't...

Parallel updates should be the default. Some extra work is needed to handle the stdout and stderr of individual update processes though. They can be both captured and only shown...

I will engage in the technical points later, but here are some comments as a moderator to @krader1961's comment above. ---- > Why ins't the `env` command (e.g., `env LS_COLORS=''...

Revisiting this, I feel the problem with `tmp` is not the amount of keystrokes but how counter-intuitive it is. It works on the enclosing lambda, so you need to first...

The methods are used in history walking mode to avoid loading the entire history into memory.

(Elvish doesn't have `fprint`, I think you misspelt `printf`? Also `errecho` and `eecho` seems transposed - that's not important though.) I'm not sure about this. I agree with you that...