71–80 of 101 posts
>But the years of using screen have ingrained in my muscle memory to use ctrl-a I still don't understand how this happened to so many people. Ctrl+a is already taken, how did anyone ever use screen without immediately changing it to something that doesn't conflict with a frequently used shell shortcut?
Earlier quoted context omitted.
You appear to have invented some other post to respond to, mine said nothing about ctrl+b.
Ctrl+b is the standard key combo for tmux, which is why that was mentioned in the article in the first place.
>But the years of using screen have ingrained in my muscle memory to use ctrl-a I still don't understand how this happened to so many people. Ctrl+a is already taken, how did anyone ever use screen without immediately changing it to something that doesn't conflict with a frequently used shell shortcut?
For the same reason (I'm using Ctrl+a in the shell), I'm using Ctrl+q as prefix for tmux. I'm quite surprised that I've never heard of anybody else using this combination.
For the vim lovers, this trick is quite good : unbind [ # free the weird binding set-window-option -g mode-keys vi # switch to vi bindings bind Escape copy-mode # ctrl-a ESC put your pane in a kind of vi normal mode bind-key -t vi-copy v begin-selection # start a visual select mode with v like in vim bind-key -t vi-copy y copy-selection # yank with y unbind p # free another weird binding bind p paste-buffer # paste w…
Earlier quoted context omitted.
I also love the new zoom pane that comes with 1.8 prefix . It comes very handy!
Didn't know about this. Love it. Appears to be prefix z for me. C-z seems to background the tmux session, which seems reasonable.
Earlier quoted context omitted.
I also love the new zoom pane that comes with 1.8 prefix . It comes very handy!
Is there an option/way to have "lables" in panes. Just like you have a info bar for windows, I would love to label my panes. Normally have a bunch of panes setup for logs, and it would be really nice to label them so i could tell what is in each pane.
For the vim lovers, this trick is quite good : unbind [ # free the weird binding set-window-option -g mode-keys vi # switch to vi bindings bind Escape copy-mode # ctrl-a ESC put your pane in a kind of vi normal mode bind-key -t vi-copy v begin-selection # start a visual select mode with v like in vim bind-key -t vi-copy y copy-selection # yank with y unbind p # free another weird binding bind p paste-buffer # paste w…
How is p a weird binding? It's a pneumonic for "previous" and works the same as it does in gnu screen, which is tux's "competitor."
For the vim lovers, this trick is quite good : unbind [ # free the weird binding set-window-option -g mode-keys vi # switch to vi bindings bind Escape copy-mode # ctrl-a ESC put your pane in a kind of vi normal mode bind-key -t vi-copy v begin-selection # start a visual select mode with v like in vim bind-key -t vi-copy y copy-selection # yank with y unbind p # free another weird binding bind p paste-buffer # paste w…
How is p a weird binding? It's a pneumonic for "previous" and works the same as it does in gnu screen, which is tux's "competitor."
I'm guessing this is autocorrect, but an autocorrect that knows 'pneumonic' (the Firefox spell-checker doesn't!) but not 'mnemonic' seems even less likely than a person who knows the first word but not the second.
Anyway, 'previous' is perhaps less likely to spring to mind than 'back' or 'reverse' or even 'last', each of which would have different mnemonics. ('Last' has a particularly good mnemonic if you keep your hands to the Holy Home Row, which is why vi users, who are most likely to worship at the Altar of the Home Row, can't use it.)
>But the years of using screen have ingrained in my muscle memory to use ctrl-a I still don't understand how this happened to so many people. Ctrl+a is already taken, how did anyone ever use screen without immediately changing it to something that doesn't conflict with a frequently used shell shortcut?
Indeed. I've been using Ctrl-\ as my Ctrl-a in screen (and occasionally tmux). Turns out that I never use that keystroke in real life.