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

Clash with default FZF install #52

Open
jackkinsella opened this issue Apr 6, 2020 · 1 comment
Open

Clash with default FZF install #52

jackkinsella opened this issue Apr 6, 2020 · 1 comment

Comments

@jackkinsella
Copy link

jackkinsella commented Apr 6, 2020

Hi, thanks for the plugin. Just upgrading from Ack vim.

Came across a namespace clash and I'd like to add a bit of information to help anyone else stumbling on the same issue.

By default, the fzf plugin also maps the command :Rg. A workaround from the fzf point of view is to make use of their optional prefix for their commands - let g:fzf_command_prefix = 'Fzf' and then call :FzfRg

I wonder if there's a way somehow avoid the clash by default by changing the vim-ripgrep internal code but without breaking your external API :Rg?

@gennaro-tedesco
Copy link

Another solution could be to expose the interface of the plugin functions so that the users can map them instead of using a command. For instance as shown here one could expose it as, say, <Plug>(vim-ripgrep#search) and users could

nnoremap ... <Plug>(vim-ripgrep#search)
:call <Plug>(vim-ripgrep#search)

instead of invoking :Rg all the times.

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