Kurtis Rader

@hanche: I'm perplexed by the assertion this proposal is a way to solve the problem documented in issue #1576. The addition of an `each-value` (and presumably `each-bytes`) function might be...

> For sure, the easiest way to resolve https://github.com/elves/elvish/issues/1576 is likely to replace the fixed size value buffer by one that might grow without bounds, unless the process runs out...

Searching for commands that mention `exactness-preserving` reminded me of this issue. Here are more problematic examples: ``` elvish -c '/' elvish -c '/tmp' elvish -c '..' ``` Most users will...

Not to mention that invalid paths do not perform an implicit `cd`; they result in a somewhat confusing exception: ``` elvish> > elvish -c '../argle-bargle' Exception: exec: "../argle-bargle": stat ../argle-bargle:...

Enhancing location mode to support a filter that puts the filter string at the top of the directory list if it corresponds to a literal directory is trivial. The hardest...

LOL! Implementing this, including a relevant unit test on Unix platforms, is straightforward. Testing it on Windows is more difficult.

I was looking at the Fish code for manipulating command history (to see how to use its approach for storing command history in a flat file to replace BoltDB and...

This can be closed since it was resolved by the fix for #1605.

Having solved the first two goals (see the pull-requests above) it isn't clear the third goal, compact single-line output, is practical since any value can be a composite type such...

> If benchmark reports a single number, it should be the average. I disagree. Especially if the single number isn't more sophisticated than a simple average that doesn't exclude outliers....