You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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
?The text was updated successfully, but these errors were encountered: