4 ms·
This seems similar to VSCode and it’s shell sessions. You need to restart VSCode to pick up new environment variables rather than just open a new shell. But at
by quickthrower2 4y ago
This seems similar to VSCode and it’s shell sessions. You need to restart VSCode to pick up new environment variables rather than just open a new shell. But at least you have a UI in your face to sort of remind you. With tmux server maybe it is less obvious that this will happen.
- kelnos 4y agoI don't think it's like that at all. It's pretty normal and expected that when you change env vars, existing shells won't pick them up. In tmux's case, it starts new shells with "old" env vars, where "old" is "whatever was present when the first tmux session was started".
- quickthrower2 4y agoI mean a new shell within VSCode wont pick up env var changes made after VSCode was launched. So it is roughly analogous: VSCode ~ tmux server VSCode shell ~ tmux pane This is all expected and ergonomic I agree.