Skip to content

vim-lastplace conflicts with vim-buffergator #16

Closed

Description

@r-learner

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"

Activity

  1. changed the title [-]vim-lastplace conflicts with [/-] [+]vim-lastplace conflicts with vim-buffergator[/+] on Jun 12, 2017
  2. farmergreg commented on Jun 12, 2017

    @farmergreg
    Owner

    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.

  3. farmergreg commented on Jun 13, 2017

    @farmergreg
    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!

  4. r-learner commented on Jun 13, 2017

    @r-learner
    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions