12 ms·
An absolute staple of my development setup, and one of those rare tools that always just seems to work. Thanks for all the work! Sidebar: if you're a die-hard
by mbillie1 13y ago
An absolute staple of my development setup, and one of those rare tools that always just seems to work. Thanks for all the work!
Sidebar: if you're a die-hard tmux user in Linux, and you do something like, say, open vim and then realize you haven't opened it in tmux, check out https://github.com/nelhage/reptyr https://github.com/nelhage/reptyr - it lets you do things like ctrl-z to background vim, start tmux, then steal the vim process into your new tmux session. Pretty cool!
- joyofdata 13y agoInstalled it today for the first time (just switched from Windows to Ubuntu) and I love it already! http://askubuntu.com/questions/423529/how-to-efficiently-switch-between-several-terminal-windows-using-the-keyboard http://askubuntu.com/questions/423529/how-to-efficiently-swi...
- bashcoder 13y agoThanks for the useful tip. I also really appreciate the power and utility of tmuxinator. [1] [1] https://github.com/tmuxinator/tmuxinator https://github.com/tmuxinator/tmuxinator
- saosebastiao 13y agoI love and use tux all the time, but for me it doesn't always just work. I regularly run into weird backspace/delete behavior when using tmux with ssh. For example, ssh from ubuntu into rhel and then running tmux will give me a completely different behavior compared to when I tmux in ubuntu and then ssh into rhel. I know that backspace/delete behavior has more to do with the terminal than tmux, but gnome terminal seems to handle it fine outside of tmux.
- mbillie1 13y agoHmm, I remember having this issue with RHEL also, but I thought it was fixed in maybe tmux 1.8... although I could certainly be wrong.
- cfallin 13y agoI've run into this a few times, too -- seems to have something to do with the termcap info for tmux's virtual term. FWIW, I was able to work around it with 'stty', e.g.: $ stty erase ^? to recognize DEL (ASCII 127, or ^?) as backspace. I have that in my .bashrc on a particular machine that gives me this problem...