Qi Xiao
Qi Xiao
In a sense, you can think of an interactive debugger in Elvish as a goose that lays golden eggs.
I agree about focusing on tracing first, it is also simpler to implement.
The Windows build has a different input reader that doesn't handle VT input sequences at all, so the bracketed paste handling code is left out too. In light of the...
Hmm, in fact the whole binary is [not loaded into RAM at once](https://stackoverflow.com/questions/31722881/is-an-entire-static-program-loaded-into-memory-when-launched). However, the latest HEAD version of Elvish does occupy roughly 14MB of RAM when started up. Older...
Some more accurate information: * On my machine, Elvish occupies slightly less than 12MB of RAM when started, not 14MB. * The culprit for the increase in RAM usage since...
I'll drop the web subprogram from the default build. See also #985.
The main program no longer includes the web subprogram. See https://github.com/elves/elvish/commit/4ac464a1682b9548a4309a14a89dd88e3dac5136 for the change in RAM consumption and binary size (it's not very big).
Hmm, `net/rpc`'s dependency on `net/http` surely explains the small magnitude of reduction.
Removing irrelevant flags from `-help` will need a bit more modularization...
According to [goweight](https://github.com/jondot/goweight), here are the two 10 largest packages that contribute to Elvish's binary size: ``` ~/go/src/github.com/elves/elvish> goweight | head -n10 3.9 MB net/http 3.8 MB runtime 1.9 MB...