Open Gigibeau opened 1 year ago
What an interesting coincidence. I faced the same issue just now, three hours after you. It is happening with all my configs. I'm including one as reference but there's nothing special to it really.
session_name: coralillo
start_directory: /some/path/that/exists
windows:
- focus: 'true'
layout: 66e2,211x58,0,0,13
options: {}
panes:
- pipenv run pytest -xvv
window_name: shell
- layout: 66e3,211x58,0,0,14
options: {}
panes:
- focus: 'true'
shell_command: nvim
window_name: editor
ran into the same issue, rolling back to older version 1.24.1 didn't work. then I tried kill tmux server tmux kill-server
, restart, tmuxp worked, maybe something releated to tmux server status?
Thank you everyone above. If we can get a way to reproduce this (perhaps on pytest) that would be very convenient.
@dcai Have you tried tmuxp v1.27.0? (New release this morning)
In regards to v1.27.0 - @categulario @Gigibeau : Does anything change with this?
@tony yes I have tried 1.27 1.25 and 1.24.1, that doesnt make any difference, only killing tmux server worked for me.
my os is macos 13.1.
@tony 1.27 did the trick for me, at least for now (:
@tony 1.27 works for me
Good to know it works now @Gigibeau and @categulario !
@dcai Can you show your tmuxp -V
and tmux -V
? Maybe there's a package that is out of date? If not perhaps you can give more info on reproducing? (Maybe you have an issue, but it's a different one, or maybe it's the same as other's have, not sure yet!)
Step 1: Provide a summary of your problem
There is a fetching error when trying to start a tmuxp session while already hosting a tmux server. No matter if I create a new session or append to the current one.
Step 2: Provide tmuxp details
Step 3: Describe the problem:
Steps to reproduce:
Already hosting a tmux server, having a xxx.tmuxp.yaml file with multiple windows and trying to execute it with
tmuxp load xxx.tmuxp.yaml
.Observed Results:
When trying to create a new session:
When trying to append the windows:
When no tmux server is running it works as usual though. This was no issue before I updated to the newest version through brew, I don't know which version I was on before.
Expected Results:
Starting the tmuxp session as usual.
Relevant Code:
Its quite a big configuration and to anonymizing it would take some time. I assume this has nothing to do with the config right? If I'm wrong I'm happy to provide it if needed (:.