Commands are not run in the correct pane

[sdelafond]

session_name: test
windows:
- panes:
  - shell_command: tmux display-message -p '#{window_index}'
- focus: true
  panes:
  - shell_command: tmux display-message -p '#{window_index}'

Both windows will show "1" as output, instead of "0" in the 1st and "1" in the second, so it appears that whichever windows has focus:true will somehow be used to actually run the commands...

[tony]

@sdelafond This happened in the most recent versions of tmux when how panes are split changed.

WorkspaceBuilder will need to get updated, because the previous way it used to split and traverse panes relied on behavior that was actually undefined.

[sdelafond]

All right, no problem. Once that's fixed I'll make sure to upload the new version to Debian ;)

[tony]

@sdelafond I mistakenly correlated #127 to this issue. #127 fixes separate issue with pane ordering in recent versions of tmux. 1.2.6 is live.

After looking closer at the behavior in the original issue, I can confirm that the behavior you pointed out still happens.

The reason why is WorkspaceBuilder creates each window and runs its commands sequentially.

In order to get this behavior to work, as listed in the YAML config, tmuxp would have to create windows ahead of time, then go back to each window and build the panes, run the commands, etc. Which is fine w/ me.

Anything in particular #217 gets in the way of? I'm just trying to gauge the urgency.

[sdelafond]

No urgency at all, I just came across this behavior and was
surprised. I'll package and upload 1.6 anyway :)

I would have to look at the code for WorkspaceBuilder, but I'm not sure
I understand why creating windows sequentially, and immediately building
their panes with associated commands (like you're describing it does in
1.2.6) doesn't result in each window having its correct #{window_index}
when queried via tmux. I'm probably missing something obvious heh...

[stale]

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.

This bot is used to handle issues where the issue hasn't been discussed or
has gone out of date. If an issue isn't resolved and handled in a certain
period of time, it may be closed. If you would like your issue re-opened,
please create a fresh issue with the latest, up to date information and
mention this issue in it.

[sdelafond]

Quick bump :)

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.

This bot is used to handle issues where the issue hasn't been discussed or
has gone out of date. If an issue isn't resolved and handled in a certain
period of time, it may be closed. If you would like your issue re-opened,
please create a fresh issue with the latest, up to date information and
mention this issue in it.

[sdelafond]

Last bump. I tried recently and the issue was still present.