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

Mappings don't seem to work #52

Closed
rr- opened this issue Jul 10, 2016 · 5 comments
Closed

Mappings don't seem to work #52

rr- opened this issue Jul 10, 2016 · 5 comments

Comments

@rr-
Copy link

rr- commented Jul 10, 2016

  1. Open a file
  2. :Dirvish
  3. Dirvish opens up
  4. :set ft? prints dirvish
  5. ...and yet, pressing <CR>, i etc. works as if it was a plain buffer.

I tried removing all the plugins and bindings. The issue persists in Neovim and Vim alike.
Using vim-plug.

Manually setting setf dirvish on unrelated buffers does conceal absolute paths into relative ones so it works to certain extent, but the bindings are missing there too.


Tested with:

rr-@tornado$ cat .testrc
call plug#begin()
Plug 'justinmk/vim-dirvish'
call plug#end()
rr-@tornado$ nvim -u .testrc

:PlugStatus shows only vim-dirvish.

@mhinz
Copy link
Contributor

mhinz commented Jul 10, 2016

Can't reproduce this with neither Neovim (v0.1.5-565-gb463fb9) nor Vim (7.4.1967) and latest Dirvish and Plug.

Is it important to open a file first? (I tested with and without, though.)

@rr-
Copy link
Author

rr- commented Jul 10, 2016

No, it's just as if ftplugin/dirvish.vim wasn't ever loaded.

@desjardinsm
Copy link

desjardinsm commented Jul 10, 2016

And :filetype says "plugin" is on?

@rr-
Copy link
Author

rr- commented Jul 10, 2016

That was it, I had to explicitly enable it with filetype plugin on. Curiously it didn't also work on empty vimrc as shown above; I thought it was on by default?...
Anyway, thanks.

@rr- rr- closed this as completed Jul 10, 2016
@justinmk
Copy link
Owner

Curiously it didn't also work on empty vimrc as shown above; I thought it was on by default?..

In neovim it is enabled by default since 0.1.4, if your init.vim and plugins don't set it to something else during startup.

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

4 participants