Skip to content
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

Closed
thewatts opened this issue Apr 8, 2014 · 24 comments
Closed

Issue with Vim Tmux Navigator? #33

thewatts opened this issue Apr 8, 2014 · 24 comments

Comments

@thewatts
Copy link

thewatts commented Apr 8, 2014

There's an issue using tmate and Vim Tmux Navigator together.

It looks like the issue is because of mismatching versions of tmate and tmux.
More info here and here.

@nviennot
Copy link
Member

nviennot commented Apr 9, 2014

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.

@mikedfunk
Copy link

+1

Mike Funk
mikefunk.com | mike@mikefunk.com

On Tue, Apr 8, 2014 at 8:30 PM, Nicolas Viennot notifications@github.comwrote:

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.

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-39925595
.

@thewatts
Copy link
Author

thewatts commented Apr 9, 2014

Thanks for the heads up, @nviennot !

@thewatts
Copy link
Author

hey @nviennot --- any progress on this by chance?

Thanks!

@nviennot
Copy link
Member

Argh.. Not yet. I got ambushed by my advisor, and I have yo do more school work.
I should have made some progress by the end of the month

@bruno-
Copy link

bruno- commented May 22, 2014

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:

# inside tmate
~ $ tmux ls
protocol version mismatch (client 8, server 7)

Thanks for all the great work!

@thewatts
Copy link
Author

@nviennot - understand how that goes for sure.

I wish I knew more about this tool so I could help! I'm a ruby dev :/

@thewatts
Copy link
Author

thewatts commented Jul 3, 2014

hey @nviennot -- any progress on this?
If not - is there any way that I could help?

@nviennot
Copy link
Member

nviennot commented Jul 3, 2014

Not yet. I'm still swamped.

Yes. The first thing to do is:

  1. update the tmux code to latest.
  2. remove libssh and msgpack libraries from the project, and use the system library instead

@mrmurphy
Copy link

mrmurphy commented Jan 8, 2015

Youch, I'm hoping for this also, but I don't think I'll be much help. @nviennot Thanks for tmate!

@nviennot
Copy link
Member

nviennot commented Jan 8, 2015

If you put this in your .bashrc / .zshrc:

if [[ $TMUX =~ tmate ]]; then alias tmux=tmate; fi 

does it help?

@mrmurphy
Copy link

mrmurphy commented Jan 8, 2015

I'm afraid it wouldn't help me much, the thing that chafes me is that I can't use pane_current_path in tmate to have new splits be in the same directory as the originating split.

It doesn't seem like aliasing tmux to tmate would solve that at all, as it's a tmux api incompatibility. Right?

@nviennot
Copy link
Member

nviennot commented Jan 8, 2015

oh I see. So for the directory split issue, you can have a quick hack:

if you have in your ~/.tmux.conf:

bind -n M-\ split-window -h -c '#{pane_current_path}'
bind -n M-- split-window -v -c '#{pane_current_path}'

put in your ~/.tmate.conf:

bind -n M-\ split-window -h
bind -n M-- split-window -v

That is, you just remove the -c ... argument.

@mrmurphy
Copy link

mrmurphy commented Jan 8, 2015

Well, I feel silly. For now then, I don't feel an urgent need for 1.9 :) I've downgraded tmux to 1.8
Thanks for your help!

@nviennot
Copy link
Member

nviennot commented Jan 8, 2015

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 :)

@mrmurphy
Copy link

mrmurphy commented Jan 9, 2015

Not a problem. Thank you! 


Sent from Mailbox

On Wed, Jan 7, 2015 at 8:36 PM, Nicolas Viennot notifications@github.com
wrote:

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 :)

Reply to this email directly or view it on GitHub:
#33 (comment)

@pmccarren
Copy link

Any plans for adopting tmux 1.9a?

@nviennot
Copy link
Member

Yes! But no time yet

@jondkinney
Copy link

+1 if only I knew C I'd love to help out :/

@daviddavis
Copy link

👍 is this the issue being used to track 1.9 support?

@christoomey
Copy link

There is a new PR in work on the vim-tmux-navigator repo that automatically detects tmate based on this snippet from @nviennot.

You can see the PR here: christoomey/vim-tmux-navigator#89

P.S. Thanks a ton for tmate @nviennot, it's great!

@nviennot
Copy link
Member

I'll update to the latest tmux soon :)

@christoomey
Copy link

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. I'll leave to @nviennot to close, but I believe this issue is resolved.

@nviennot
Copy link
Member

nviennot commented Jan 3, 2016

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.

@nviennot nviennot closed this as completed Jan 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants