startup_command is sent too early, even when zsh is not ready to receive it

[johmsalas]

What happened?

When I use startup_command & zsh, I expected Sesh to send the command when zsh is ready to receive it but the command is sent too early!

I must admit, this issue is partly due to my zsh taking 1 second to load. While I am currently profiling my zsh to improve its performance, it would be beneficial if Sesh could offer a mechanism to wait for the shell to fully initialize. This way, users would not need to individually optimize their zsh startup time.

I previously faced a similar situation with tmuxp, and the solution was adding a 0.5s delay before executing the command, as suggested by a tmuxp user.

Screen.Recording.2024-10-03.at.11.20.55.AM.mov

Version

sesh version dev

Relevant log output

No response

Reviewed

• Reviewed existing issues and made sure this bug has not already been submitted.
• I have read the documentation and understand how sesh works before submitting this bug

[joshmedeski]

I think it's an important improvement to wait for the shell to load.

I'm wondering if under-the-hood we could use $SHELL to execute the function independently of the tmux window loading.

I'll have to experiment with it and get back to you, thanks for the info.