3 ms·
I 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 sta
by kelnos 4y ago
I 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.