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

vim-lastplace conflicts with vim-buffergator #16

Closed
r-learner opened this issue Jun 12, 2017 · 3 comments
Closed

vim-lastplace conflicts with vim-buffergator #16

r-learner opened this issue Jun 12, 2017 · 3 comments

Comments

@r-learner
Copy link

r-learner commented Jun 12, 2017

The recent commit conflicts with vim-buffergator.

Error detected while processing function <SNR>38_lastplace:
line    2:
E16: Invalid range
E16: Invalid range

The conflict was introduced at the commit f1c8989ea6af5ed297d7d622d190a86cc86f7681, the commit 36c4ae38130232134ece7bdd0e844d8034b585ab works.

Maybe I could change the default setting to ignore vim-buffergator list window, but I do not know vim-buffergator list window type or name.

    let g:lastplace_ignore = "gitcommit,gitrebase,svn,hgcommit"
    let g:lastplace_ignore_buftype = "quickfix,nofile,help"
@r-learner r-learner changed the title vim-lastplace conflicts with vim-lastplace conflicts with vim-buffergator Jun 12, 2017
@farmergreg
Copy link
Owner

farmergreg commented Jun 12, 2017

Hi @r-learner thanks for the bug report! Can you give me detailed steps to reproduce this problem? I have the latest version of vim-buffergator installed and it is working for me when I use <leader>b to open the window that lists all open buffers.

@farmergreg
Copy link
Owner

@r-learner I was able to reproduce it on a system that is running an older vim than the one I originally tested on. Please let me know if this fix solves your problem. Thanks!

@r-learner
Copy link
Author

Thank you very much. The commit works well on neovim.
Btw, I am using neovim v0.2.0.

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

2 participants