* On 31 Mar 2010, Nicolas Williams wrote: > > This is all completely OT, but... using <ctrl-b> is an absolute > non-starter as it's an emacs-mode editing character. I've been using
Ctrl-a is an absolute non-starter too, because it's an emacs-mode line-editing character. :) Which is why you rebind no matter which screen mux you use. > screen for almost two decades now. The lack of quick access to screens > past 9 is somewhat annoying, but I can live with that. Same with > buffers. So I doubt I'll switch, but I may give it a try sometime just > to see. I've been using screen for almost two decades, too, but in pretty much the same way I've been using bash: every year, I keep using it because it's what I've been using for the last N-1 years and the activation energy to change is too high. Most of the functionality I need from screen is just the virtual terminal emulation and the detaching/reattaching feature. I find the multiplexing per se more of an annoyance (sometimes I accidentally use it) than a feature, because I have used various home-grown front-ends for screen for most of the two decades, and that's where all my real control and capability comes from. Muxing is easy to do outside of the emulation/detaching layer, so why keep them together? I simply haven't taken the time to swap out screen for dtach or tmux yet. Screen also has the advantage of already being available on a LOT of systems either natively or through precompiled distribution channels. This is partly why I haven't changed to something lighter-weight. What I *really* want is to combine the vty and socket detach feature with my front-end, ideally in a python program that I don't need to compile for every platform I move to. But that's pretty far down my back burner queue. -- -D. [email protected] IT Services University of Chicago
