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
Similar to #61. When opening a new tmux session from another tmux session (both using tmuxifier), the first session_root is honored in the second session. For example:
# Filename: fizz.session.sh
session_root "~/workspace/fizz"if initialize_session "fizz";then#1 pane:# - ssh connection to remote server, then connect to screen running an IRC client
load_window "irc"fi# Finalize session creation and switch/attach to it.
finalize_and_go_to_session
# Filename: buzz.session.sh
session_root "~/workspace/buzz"if initialize_session "buzz";then#1 pane:# - something to open vim with
new_window "editor"fi# Finalize session creation and switch/attach to it.
finalize_and_go_to_session
When running tmuxifier s fizz, it loads the predefined fizz session just fine with the default path being ~/workspace/fizz for all new windows. I open a new window within tmux and run tmuxifier s buzz and it opens the predefined buzz session with the path remaining as ~/workspace/fizz. All subsequent windows in that session have paths of ~/workspace/buzz, however.
If spawning the buzz session is run outside of the fizz session, this problem does not occur. It does, though, show there is a bug with the idempotence of tmuxifier session generation.
The text was updated successfully, but these errors were encountered:
Similar to #61. When opening a new tmux session from another tmux session (both using tmuxifier), the first session_root is honored in the second session. For example:
When running
tmuxifier s fizz
, it loads the predefined fizz session just fine with the default path being~/workspace/fizz
for all new windows. I open a new window within tmux and runtmuxifier s buzz
and it opens the predefined buzz session with the path remaining as~/workspace/fizz
. All subsequent windows in that session have paths of~/workspace/buzz
, however.If spawning the buzz session is run outside of the fizz session, this problem does not occur. It does, though, show there is a bug with the idempotence of tmuxifier session generation.
The text was updated successfully, but these errors were encountered: