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

double click buffer will open other file named "No name" #15

Closed
CaoPeng opened this issue Jan 6, 2016 · 5 comments
Closed

double click buffer will open other file named "No name" #15

CaoPeng opened this issue Jan 6, 2016 · 5 comments

Comments

@CaoPeng
Copy link

CaoPeng commented Jan 6, 2016

  1. Open 2 (or more) files
  2. :bnext / :bprev to switch buffer → ok
  3. Try double click/click the buffer to switch buffer → KO
    → opens another file named "No name"
@ap ap added the bug label Jan 6, 2016
@ap ap closed this as completed in 7c5e2c9 Jan 6, 2016
@ap
Copy link
Owner

ap commented Jan 6, 2016

Thanks for prodding me into giving this another shot. I was all set to explain how this was not a bug I could fix, because it’s just how the tabline in Vim works, and plugins cannot control that. And that is still true. But I could use some of Vim’s builtin behaviour against itself, which had not occurred to me until now. So your bug ticket made the plugin better. Thank you!

@ap
Copy link
Owner

ap commented Jan 6, 2016

Oh – it will however still not allow you to switch tabs by clicking on them. I have tried to make that work and failed. I have explained more in #6.

It looks like NeoVim may allow this at some point (according to neovim/neovim#3871) but stock Vim does not.

@regedarek
Copy link

any updates after neovim 0.2.0?

@ap
Copy link
Owner

ap commented Jul 6, 2017

It wasn’t on my radar, so no, but thanks for the ping. I’ll take a look into what was implemented in NeoVim whether and how I can use it.

@ap
Copy link
Owner

ap commented Jul 6, 2017

@regedarek: I’ve added #32 to track this, so you can watch that if you want to be updated.

@ap ap added the resolved label Jan 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants