-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tmuxinator Conflict #249
Comments
I have been able to determine that whatever was changed from v.0.304 to v.0.305 is when the problem began to occur. |
Ah interesting, thank you for opening this bug! I tried to reproduce this with this tmuxinator config:
And for me, things seem to be working as I'd expect where I see both of those echo commands get executed. Can you share a bit more about your tmuxinator config and exactly what behavior you're observing? Also what tmuxinator, tmux, and shell versions you're using might be helpful. Thank you! |
I believe I have narrowed down the problem. It's something to do with setting the TERM variable. NOTE: the Here's my sample configuration, some items redacted. I took out all my other crazy configuration and narrowed it down to barebones. Everything else in my config doesn't seem to be an issue. I think you can replicate the problem using this configuration. versions:
~/.zshrc:
~/.config/tmuxinator/test.yml
~/.tmux.conf
This screen recording might also be helpful. |
With tmuxinator I used to be able to have a command initially run when a window/pane was created. After updating hishtory to 0.311 the command prints in the window but never executes. If I comment out the
source /home/user/.hishtory/config.zsh
from my .zshrc file it works fine, but of course hishtory does not. I wish I could downgrade hishtory to tell you what version it was working on but I don't know how to do that.edit: I have been able to rollback my virtual machine and confirm things were working correctly in v0.297
The text was updated successfully, but these errors were encountered: