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

:Ack shows 'Unknown option' warning in quickfix list in neovim #9

Closed
dsummersl opened this issue Jul 17, 2015 · 8 comments
Closed

:Ack shows 'Unknown option' warning in quickfix list in neovim #9

dsummersl opened this issue Jul 17, 2015 · 8 comments
Labels

Comments

@dsummersl
Copy link

When I use :Ack <search> in nvim it shows the following warning at the end of the quicklist:

|| nvim: Unknown option argument: "--servername"
|| More info with "nvim -h"

:Acks and navigation seems to work fine tho...

@wincent wincent added the neovim label Jul 17, 2015
@ntnn
Copy link
Contributor

ntnn commented Jul 17, 2015

Thats an issue with popes vim-dispatch and neovim, if you turn off dispatch (let g:FerretDispatch = 0) it won't happen (and also not be working asynchronous). I've mentioned the same (and also that it then tends to not show the result in quickfix).

I also tended toward making a PR to use xolox' vim-misc async feature, if its available (it works great in neovim and I'm writing two plugins which are taking advantage of it).

@wincent
Copy link
Owner

wincent commented Jul 17, 2015

Thanks for the report @dsummersl! I haven't used Neovim myself yet, so I'm looking for help ironing out issues like these. I do mean to dig into myself soon, but if you beat me to it I'd be happy to accept a PR.

Does this happen for all searches, even simple ones like :Ack foo?

Not sure where the --servername thing is coming from; it's not from Ferret itself.

@wincent
Copy link
Owner

wincent commented Jul 17, 2015

Thats an issue with popes dispatch.vim and neovim

Ah, thanks for shedding light on this, @ntnn. Do you think this is a bug in upstream dispatch.vim that we should report upstream?

@dsummersl
Copy link
Author

Just figured out the vim-dispatch connection myself - yeah its happening with simple searches.

@ntnn
Copy link
Contributor

ntnn commented Jul 17, 2015

@wincent Since dispatch itself works with neovim my best guess is that it's detection of the type of vim doesn't work with ferret, hence using the client/server architecture of vim - someone would need to take a look at that and see where exactly it fails.

@dsummersl Does it exclusively happen with simple searches or also with more complicated regexes?

@dsummersl
Copy link
Author

Happens with regexes too.

@wincent
Copy link
Owner

wincent commented Jul 17, 2015

gilbertwyw added a commit to gilbertwyw/dotfiles that referenced this issue Jan 5, 2016
Remove 'ferret' as its current support for NeoVim is not good

Reference:

- wincent/ferret#9
- rking/ag.vim#85
@wincent
Copy link
Owner

wincent commented Mar 7, 2016

Going to close this as I can't repro this with:

  • NVIM 0.1.1 (compiled Jan 2 2016 22:49:49).
  • Ferret 1.1.
  • dispatch.vim current HEAD of master (eb3e564).

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

No branches or pull requests

3 participants