4 ms·

there's truecolor support (which is now available in screen 5) and the other thing is clipboard support (not sure what it's called exactly) which basically allo

by sirfz 2y ago

there's truecolor support (which is now available in screen 5) and the other thing is clipboard support (not sure what it's called exactly) which basically allows you to directly copy text from screen (or say, neovim) even from remote sessions. Can't think of anything else personally (oh there's undercurl support if you care about that). I find screen to be more stable than tmux but can't say I had any issues with tmux in the past couple of years (but it bothers me that tmux sessions share the initial environment the first session was launched from iirc). Right now it's the clipboard support that makes me use tmux over screen.

somat 2y ago
> but it bothers me that tmux sessions share the initial environment the first session was launched from. It does do this, but I am curious what would be better? I heard this complaint before and It baffles me. let me explain. environments are... sticky, a child process inherits it's parent processes environment. so the tmux server starts and inherits the environment from the shell that started it, then each pane inherits the environment from the tmux server. As far as I can tell you want each pane to inherit the environment from somewhere else but can't figure out why or how that would happen. My best guess is that you want tmux-attach to stash the environment it was ran in so that tmux could then use that when making new panes. my second guess is that you want tmux to use the current pane as the parent process for a new pane. both of which sounds like it would be even harder to control the tmux environment.
- sirfz 2y ago
  Any changes to ~/.bashrc or even ~/.tmux.conf would not reflect in any newly created session unless you terminate all sessions and start afresh. In screen, every new session starts from the current host environment which is more convenient
  - somat 2y ago
    Not sure what bash is doing but tested with ksh and it runs and picks up changes in both .profile(login shells) and .kshrc(all shells) so I don't think it is tmux that is interfering with that aspect. In fact I was a bit surprised that .profile ran on every created pane, as naively I would not have thought that would be a login shell. not sure about the rest, I did read the man page again, and wow there is a lot more configurabilty than I first thought, however I found nothing great, the best I could come up with is. bind c 'source-file /home/xxx/.tmux.conf; new-window'

by sirfz 2y ago

somat 2y ago

> but it bothers me that tmux sessions share the initial environment the first session was launched from. It does do this, but I am curious what would be better? I heard this complaint before and It baffles me. let me explain. environments are... sticky, a child process inherits it's parent processes environment. so the tmux server starts and inherits the environment from the shell that started it, then each pane inherits the environment from the tmux server. As far as I can tell you want each pane to inherit the environment from somewhere else but can't figure out why or how that would happen. My best guess is that you want tmux-attach to stash the environment it was ran in so that tmux could then use that when making new panes. my second guess is that you want tmux to use the current pane as the parent process for a new pane. both of which sounds like it would be even harder to control the tmux environment.

sirfz 2y ago
Any changes to ~/.bashrc or even ~/.tmux.conf would not reflect in any newly created session unless you terminate all sessions and start afresh. In screen, every new session starts from the current host environment which is more convenient
- somat 2y ago
  Not sure what bash is doing but tested with ksh and it runs and picks up changes in both .profile(login shells) and .kshrc(all shells) so I don't think it is tmux that is interfering with that aspect. In fact I was a bit surprised that .profile ran on every created pane, as naively I would not have thought that would be a login shell. not sure about the rest, I did read the man page again, and wow there is a lot more configurabilty than I first thought, however I found nothing great, the best I could come up with is. bind c 'source-file /home/xxx/.tmux.conf; new-window'