Usage with vim/neovim and fzf.vim

[chopfitzroy]

I am trying to set this up with fzf.vim and as per this comment rg does not seem to currently work.

I was hoping you would have some insight into this?

Cheers.

[junegunn]

Another problem I noticed is this:

I don't think it's intentional?

[mengelbrecht]

You mean the missing line numbers? If the output is not to a tty the parameter for line numbers -n has to be explicitly specified.

[BurntSushi]

Yes, it is intentional. When searching at a tty, line numbers, headings and colors are enabled by default. Otherwise, the default format is the same as git grep.

I otherwise don't know what the problem is here. Could you please describe it in more detail?

[junegunn]

I see, so then it's not a problem. The issue we have is that the output of rg (0.1.17) is not captured by system() function of vim unlike grep or ag.

:echo system('ag foo')
:echo system('grep foo *')

:echo system('rg foo')

EDIT:

ag foo < /dev/null
grep foo * < /dev/null
rg foo < /dev/null

[BurntSushi]

I think rg and grep actually have the same behavior here. If you pass a file path argument, then stdin is ignored. The issue here is what happens when no path is given. Here's an illustration:

$ echo PM_RESUME | ag PM_RESUME | wc -l
1
$ ag PM_RESUME < /dev/null | wc -l
16
$ echo PM_RESUME | rg PM_RESUME | wc -l
1
$ rg PM_RESUME < /dev/null | wc -l
0

I bet this is the same bug that's being seen in #35.

[BurntSushi]

Hooray, this is indeed a dupe of #35! Fixing this fixes that too.

[BurntSushi]

Weird. Github didn't close this. Fixed in ab0d1c1.

[chopfitzroy]

So just to clarify does rg need to be invoked with --column or --no-heading for this to now work?

Going of #35..?

Cheers.

[BurntSushi]

@CrashyBang I don't think the problem has actually been explained to me, but I imagine you'd want rg --no-heading --vimgrep.

[chopfitzroy]

Hey @BurntSushi okay sweet will go over as soon as I am home from work will let you know how it goes hoping to do a write up on medium rg has already massively supercharged my workflow.

[BurntSushi]

@CrashyBang glad to hear it! Please send a link over if you do that write up. :-) (I'd also be happy to read a draft.)

[chopfitzroy]

Hey @BurntSushi write up here: https://medium.com/@crashybang/supercharge-vim-with-fzf-and-ripgrep-d4661fc853d2 sorry wanted to get it up but still making tweaks if needed.

[junegunn]

@CrashyBang I would advise against suggesting -i and -e as the default. fzf by default performs smart-case matching which is really handy with CamelCase files. -i disables that and makes the search always case-insensitive. You might also want to experiment without -e especially because of the new scoring mechanism introduced in 0.15.0.

[chopfitzroy]

Hey @junegunn noted and removed :).

Otherwise it is okay?