The release notes don't say:
Is this a session-breaking update?
I'd hate to run the update only to have it kill my current TMUX session.
Devs - if you're reading this: PLEASE indicate if I could update without restarting the session.
Tmux 2.0 released
21–30 of 221 posts
Re: Tmux 2.0 released
#22For those who are just getting started with tmux: I advise looking around others' .tmux.conf files for some sensible settings. Like Vim, Tmux ships with a lot of powerful features disabled by default. My absolute favorite has to be binding a hotkey to opening URLs in the current window [0]. See [1] for a small demo I just recorded. To get started, here's my current config: [1] [0]: https://github.com/jbnicolai/tmux/b…
You use ctl+s as your bind?
I do. It's closer to the prefix/leader I was used to when using screen (), and I find it easier to type.
Re: Tmux 2.0 released
#23I don't see anything about it, so I'm assuming there's still no support for "true" (24 bit) colour? Would really love if they added that, since Neovim now supports it.
Re: Tmux 2.0 released
#24Why it's 2.0? I don't see any really significant changes, or maybe I missed smth.
Maybe because Tmux 2.0 has some breaking changes??
They broke features between releases before without increasing the major version number.
While trying to use the same .tmux.conf over multiple versions of tmux 1.x, I often had to adapt the config file to settings being renamed or just going away without a deprecation warning beforehand.
Re: Tmux 2.0 released
#25Re: Tmux 2.0 released
#26Earlier quoted context omitted.
Maybe because Tmux 2.0 has some breaking changes??
like what?
Incompatible Changes
====================
* The choose-list command has been removed.
* 'terminal-overrides' is now a server option, not a session option.
* 'message-limit' is now a server option, not a session option.
* 'monitor-content' option has been removed.
* 'pane_start_path' option has been removed.
* The "info" mechanism which used to (for some commands) provide feedback
has been removed, and like other commands, they now produce nothing on
success.Re: Tmux 2.0 released
#27Re: Tmux 2.0 released
#28Earlier quoted context omitted.
Is this a feature in 2.0? It doesn't seem to work for me - I still see a large part of my terminal window filled with the dots, since the other session's terminal window is much smaller.
Ah, I forgot to mention: the resize -if the terminal-window is smaller- will still happen, but as long as the two sessions are operating on a different window they can be of different size.
I think I'm missing something.
Terminal A: 300x10 lines (long across, but short) Terminal B: 120x30 lines (standard new terminal size)
I have a tmux session running in A; I open terminal B, and attach to it with -new-session. My first pane is trimmed to the height of Terminal A.
If I do prefix-c (create new pane), the new pane is now the size of Terminal B - hurray!
But if I open Terminal C, which is yet another size, and attach to my existing session, it resizes every pane in Terminal B to the size of Terminal C; and when I disconnect from Terminal C, those panes do not appear to switch back to what they now should be, unconstrained by Terminal C.
(If I didn't explain this clearly, I can provide some screenshots later.)
Re: Tmux 2.0 released
#29I'm looking forward to the combination of Tmux and Neovim. Both (will) support detached/shared sessions, both are scriptable/configurable, both can be driven by a remote process. I believe with Tmux and Neovim you could put together anything from a simple test/editing environment to a full-blown IDE.
But you can already script vim...
Re: Tmux 2.0 released
#30Earlier quoted context omitted.
I do. It's closer to the prefix/leader I was used to when using screen ( ), and I find it easier to type.
Why not use C-a?
I assume ctrl-s is easier to press than ctrl-a, I have trouble with ctrl-a on Mac with reconfigured CapsLock, and my bind key is ctrl-space.