101–110 of 121 posts
Earlier quoted context omitted.
And now you can use tmux in Cygwin.
I've been using it in Cygwin for a long time. What is supposed to be broken?
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 - it lets you do things like ctrl-z to background vim, start tmux, then steal the vim process into your new…
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 - it lets you do things like ctrl-z to background vim, start tmux, then steal the vim process into your new…
I 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 see…
Has anyone used these, and can they give me a comparison: tmux/scree/byobu Currently a byobu user, it seems fine so far. Wondering what others offer more than that.
tmux is very scriptable. I have a shell script "go". go opens new tux window splits it twice (3 total panes) all ssh'd into box, one as root, one tailing log files. The "go" script has grown over time, running custom log tails on specific boxes. And one command "vroom" which ssh's into web and db boxes running atop, apachetop, pg_activity in a bunch of panes. It's just an example. Tux lets you automate interactive sh…
I remember using on the mac a branch of tmux with iTerm, where the gui understood tmux, giving native tabs and scrollback. I thought this was the greatest thing ever, but am now on Linux. Is this work still continuing does anyone know?
Can someone share a use case or example of using tmux? Sorry for being thick, but I'm just not getting it. I use iTerm. I use ssh to regularly access about 20 other boxes. I create tabs for every task. So I might have 3 tabs for a single box. 1 to start/stop processes, 1 to edit files, 1 to tail logs to verify my crap's working. I installed tmux and I couldn't figure out what I'd use it for. This might be completely…
This should synchronize the input to all panes i.e. type in any one and it will be sent to all 5. to turn it off, just run the same command again. I don't know if tmux has equivalent synchronize-windows.
This kind of annoys me, but I'm successfully using this workaround (hinted at in the announcement):
bind c run 'tmux new-window -c "#{pane_current_path}"' bind-key '%' split-window -hc "#{pane_current_path}" bind-key '"' split-window -vc "#{pane_current_path}"
Anyone know why this change was made?
Earlier quoted context omitted.
I've been using it in Cygwin for a long time. What is supposed to be broken?
That's strange. The patch that allows it to work has only existed for less than a year. Tmux apparently passes file descriptors over unix domain sockets, which isn't supported by Cygwin.
I have to say that the tmux-users mailing list in general, and Nicholas Marriott in particular, are really nice and friendly. I had a feature request (256 colors in fbterm so you can get 256 color tmux/vim without x), quickly got patch code, got support (I had never used patch before and didn't tell it to ignore whitespace) and when it worked, was told it would be in 1.9, and there it is. :-)
I'm blaming you =P
In all seriousness actually trying to get 256 colour mode auto detecting and working reliability across different xterms, tmux/screen, ssh and so on, without some hack that forces the 256 on even when it's not supported seems impossible :/
I added the following to my zshrc, which seems to have helped. Why don't these terminals report 256 color mode by default?
if [ "$COLORTERM" == "yes" -a "$TERM" == "xterm" ]; then
export TERM=xterm-256color
fiEarlier quoted context omitted.
I find that if I run emacsclient and emacs server, I don't need to use tmux. If I get disconnected, I just reconnect and run emacsclient again. All my buffer states are preserved.
Yeah, as an emacs user, every time a tmux post pops up on HN, I go read about it and wonder what it would really do for me. I guess what I'm seeing is that for my emacs sessions it really doesn't buy me anything. I'd be curious to hear about things I can do with tmux that I can't do with emacsclient and emacs daemon.