Harald Hanche-Olsen

> At least being about to parse output of `/usr/libexec/path_helper` on Mac Instead of running the program, I just duplicate its functionality myself: ``` set @paths = ~/.local/bin ( put...

@krader1961 Yeah, I thought of that optimization too, but neglected to mention it, as I was in a rush to leave. Of course, it comes at a slight cost in...

Yes, please! But also, being able to get just the command arguments would be really useful. Such as, `randint $low? $high` or `range &step=1 $low? $high`, as a simple reminder...

> Actually, would it be a better approach to attach the metadata we normally get with elvish fns (eg arg-names, body, def, etc) to the builtins? Then add an optional...

I think `help unknown-command` should just print a (possibly styled red or something) text saying the command is unknown, rather than try to be super helpful and run `man`. Once...

@krader1961 wrote: > I'm ambivalent about special-casing `help unknown-command` to not raise an exception and instead simply write an error message to stderr. Doing so is arguably the more user...

What should `del x[$i]` do? Shift the remaining list members left, so the list is one item shorter? But that would have a rather different semantics than the similar operation...

Hmm, that's an interesting point. I had forgotten, or possibly never learned, that `var f = /bin/echo; $f 42` is legal. On the other hand, `var f~ = /bin/echo` is...

``` ⬥ keys $str: | to-lines | sort | all ⮕ compare~ ⮕ contains-any~ ⮕ contains~ ⮕ count~ [… and so on …] ``` But of course you knew that...

A quick suggestion, similar to `compact` but perhaps marginally better: `tighten`.