Kurtis Rader

I'm not convinced of the need, or value, of a builtin debugger. But something like the `-x` flag supported by most (all?) POSIX shells to enable command tracing is definitely...

No doubt an interactive debugger would add value. But, like you @xiaq, I almost never use a debugger other than to examine a process core dump (or kernel crash dump)....

The "question" label should probably be removed as this is fundamentally an enhancement request. I've been working on a "debug" package to replace the existing use of the current "logutil"...

The documentation needs clarification. A `catch` or `finally` block is always required. Try ``` try { nop } catch { nop } else { echo well } ``` Also, the...

Whether `try-finally-else` should work is debatable. Personally, I am opposed to allowing the clauses appear in every possible ordering. Why not `finally-try-else`? As long as the documentation is clear I...

Note that this was [requested](https://github.com/elves/elvish/issues/554#issuecomment-492944781) in issue #554 but not implemented because the solution to that issue focused on the basic functionality. I would also argue that, since Elvish does...

On my macOS server starting an interactive elvish shell built from Git head as I type this, with a modest number of modules (mostly from those documented at https://github.com/zzamboni/dot-elvish), results...

@xiaq, How do you feel about making a web accessible Elvish shell a separate program rather than a feature enable via `elvish -web`? Doing that should reduce the overhead of...

With your recent change I see a 4% decrease in file size and a 3% reduction in initial RSS on macOS. Which is a surprisingly small decrease. The core Go...

https://github.com/urld/fatdeps provides a graph of package sizes and dependencies in the elvish binary. It confirms that net/http (13% of the binary) is included only as a consequence of using net/rpc...