Qi Xiao

Some use cases: * Updating Elvish to a newer version. * Preserving Elvish sessions across machine reboot

Well, this could easily have more use cases... * Tweak Elvish interactively, and dump your configuration into a file. This is now your `rc.elv`. * Define a function interactively, and...

I totally agree that this should not be the default behavior of `exec`; in fact, what you are proposing is exactly what I have in mind. You can already implement...

@krader1961 there are two reasons: * Consistency in form: all modules must be imported before use. Granted, the builtin namespace is special, but its specialty goes beyond just being "pre-imported";...

Hmm, the reason it's this way is that if the user typed a `/` it could be intentional and Elvish should respect that. You can always get `\` by, well,...

> > Hmm, the reason it's this way is that if the user typed a `/` it could be intentional and Elvish should respect that. You can always get `\`...

Not going to respond to every issue discussed here - the correct mechanism for implementing virtualenv support would be asking the user to `eval` a file, not `use` a module....

Hmm yes the `edit:` module is weird for historical reasons, it's not an importable module, but a special module directed put in the global namespace in interactive mode. Allowing `use...

It's already possible to index with multiple expressions; $a[(seq 1 2 10)] extracts the first five evenly numbered items. I am with @hanche in that `get $n` should only output...

Sorting sounds good. Regarding how to sort, I'm not convinced of the ROI of adding *any kind of smartness*, and I feel we should just use [sort.Strings](https://godoc.org/sort#Strings), which sorts by...