Kurtis Rader

> You can see why the order matters. No, I can't. 😄 The order of options, pretty much by definition, does not matter. It seems to me you are misusing...

Having slept on the idea I've decided there should be a `$before-external-cmd` and `$after-external-cmd` pair of callback lists. In the before variant each callback in the list is called with...

The callbacks should include additional info to make it easier to know the context in which the external command is being run; e.g., which module, script, or interactive context invoking...

Note that there are two cases to consider: 1) Elvish scripts, and 1) Interactive Elvish sessions. The first case can be dealt with by having the Elvish compiler behave like...

FWIW, I was going to implement this feature but decided not to because I still hope that issue #1222 is resolved. Thus eliminating the need for an Elvish daemon by...

I'm closing this because I hope my work to replace the Elvish daemon and dependency on the BoltDB project is merged in the not to distant future which will make...

The reason for the `./tools/check-gen.sh` failure is because the generated file, *pkg/sys/ewindows/ztypes_windows.go*, contains this line: ``` // cgo.exe -godefs C:\Users\xiaq\on\elvish\pkg\sys\ewindows\types.go ``` It should apparently contain this line: ``` // cgo.exe...

Playing devil's advocate: It still seems the simplest, easiest to understand and maintain, option is to simply run `make all-checks` on every platform in the CI test matrix rather than...

I wholeheartedly agree that a solution to this problem is needed. Especially since I'm always running a bleeding edge developer version of Elvish. But, before anyone rushes off to add...

Also, I appreciate one reason for the current behavior is to support examples like these: ``` elvish> var l = [] elvish> eq $@l ▶ $true elvish> var l =...