2 ms·
The one thing keeping me from switching is the lack of command classes[0]. I want to be able to chain bindings, so "^a s a" does "ssh server-a", and "^a s b" do
by lkbm 8y ago
The one thing keeping me from switching is the lack of command classes[0]. I want to be able to chain bindings, so "^a s a" does "ssh server-a", and "^a s b" does "ssh server-b".
People keep telling me that tmux is better (though I still don't understand why), but I lean heavily on chained bindings and haven't found a solution in tmux.
[0] http://aperiodic.net/screen/interface#command_classes http://aperiodic.net/screen/interface#command_classes
- cik 8y agoTotally fair, and I never missed it because I have a different approach. I always open the shell and execute my commands in it - regardless of screen/tmux, a straight bash shell, or xterms(etc). I have a crazy amount of automatic generating shell commands, so that I basically need bash --login to trigger anyways.