-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Issue with Vim Tmux Navigator? #33
Comments
Arh... I haven't upgraded tmate to the 1.9 yet. And there is a ton of things that need some fixing. I'll have some more time after May 1st. I apologize for the lack of updates. |
+1 Mike Funk On Tue, Apr 8, 2014 at 8:30 PM, Nicolas Viennot notifications@github.comwrote:
|
Thanks for the heads up, @nviennot ! |
hey @nviennot --- any progress on this by chance? Thanks! |
Argh.. Not yet. I got ambushed by my advisor, and I have yo do more school work. |
Hi, I just noticed this issue with tmux version mismatch today. Btw I don't run vim navigator, but the root problem is the same I think. You probably already know this, but for the sake of documentation, here's how to reproduce:
Thanks for all the great work! |
@nviennot - understand how that goes for sure. I wish I knew more about this tool so I could help! I'm a ruby dev :/ |
hey @nviennot -- any progress on this? |
Not yet. I'm still swamped. Yes. The first thing to do is:
|
Youch, I'm hoping for this also, but I don't think I'll be much help. @nviennot Thanks for tmate! |
If you put this in your .bashrc / .zshrc: if [[ $TMUX =~ tmate ]]; then alias tmux=tmate; fi does it help? |
I'm afraid it wouldn't help me much, the thing that chafes me is that I can't use It doesn't seem like aliasing tmux to tmate would solve that at all, as it's a tmux api incompatibility. Right? |
oh I see. So for the directory split issue, you can have a quick hack: if you have in your
put in your
That is, you just remove the |
Well, I feel silly. For now then, I don't feel an urgent need for 1.9 :) I've downgraded tmux to 1.8 |
updating tmate to tmux 1.9 is really on my list, but I'm being a little conservative because I'm not sure what could break and all that. I don't want to introduce regressions, because I know I won't have the time to deal with them. Sorry about that :) |
Not a problem. Thank you! — On Wed, Jan 7, 2015 at 8:36 PM, Nicolas Viennot notifications@github.com
|
Any plans for adopting tmux 1.9a? |
Yes! But no time yet |
+1 if only I knew C I'd love to help out :/ |
👍 is this the issue being used to track 1.9 support? |
There is a new PR in work on the vim-tmux-navigator repo that automatically detects You can see the PR here: christoomey/vim-tmux-navigator#89 P.S. Thanks a ton for tmate @nviennot, it's great! |
I'll update to the latest tmux soon :) |
Follow up for anyone using Vim Tmux Navigator. I've gone ahead and merged the fix (christoomey/vim-tmux-navigator#89) so if you pull locally all should be set. This works with the current |
tmate has been upgraded to latest version of tmux. Run brew install --HEAD tmate if you use homebrew. Install from sources (git HEAD) if not. |
There's an issue using
tmate
and Vim Tmux Navigator together.It looks like the issue is because of mismatching versions of
tmate
andtmux
.More info here and here.
The text was updated successfully, but these errors were encountered: