You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but that doesn't work either. I can see the argument for not allowing duplicate session/window name instances, but the with unique window names it should work.
It's been a long time since this was posted. Not sure if it's still the case or not - but I suppose so
Note that this does work if I specify a unique session name for each yml
So it worked then. If so, that makes sense with the current behavior.
Right now - tmuxp treats workspace files with the same session_name as already loaded. They need to be named differently. Perhaps we can change that assumption (I'm redoing the test infrastructure and loading code in other PRs)
@tony Appreciate the mental bandwidth of working through the post.
My argument for the change is be the ability to append to an existing session programmatically, vs needing to create a new session just to add a window, that really belonged on the existing session.
I want to have a session names "envs" that I hang multiple windows off of, each with a few panes to connect to an target env.
Each time I run
tmuxp load -y /Users/edgeb1/.tmux/<env filename>
I expect to get a new window added to the same session.Here's a snippet of the yaml for env1:
and repeated again for env2:
Identical, except for the
window_name
.Such that my session tree should look like:
"a-local" is the default session.
I load these using:
tmuxp load -y /Users/edgeb1/.tmux/env1.yml
tmuxp load -y /Users/edgeb1/.tmux/env2.yml
But what happens is that only the 1st one loads.
Afterwards I have this:
Or, if I reverse the order of the commands and instead run:
tmuxp load -y /Users/edgeb1/.tmux/env2.yml
tmuxp load -y /Users/edgeb1/.tmux/env1.yml
Then I get this:
Same applies if I try load to yml files on the same cmdline:
Note that this does work if I specify a unique session name for each yml:
and repeated again for env2:
Then I get:
AFAICT, I should be able to load additional yml configs that append new windows to an existing session.
It does "something" on the 2nd failed load is it always switches to the "envs" session, and shows the one window that's there.
I would expect to be able to load the same yml, say env1, over and over and keep getting new windows with the same name:
but that doesn't work either. I can see the argument for not allowing duplicate session/window name instances, but the with unique window names it should work.
Step 2: Provide tmuxp details
tmuxp debug-info
The text was updated successfully, but these errors were encountered: