Grepper{Ack,Pt,Rg} are async in Neovim, but not Vim

[habamax]

vim8 and windows 10

pt is installed.

Trying to

:GrepperPt something<CR>

returns nothing although there is 'something' in the file.

Next thing is:

:GrepperPt<CR>

Error detected while processing function <SNR>77_on_exit:
line 10
E108: No such variable: "s:id"

[mhinz]

Unfortunately I can't test for Windows.

Is pt --nogroup something working manually?

(As for the second problem, it's most probably a follow-up issue. I'll add a fix for it anyway.)

[habamax]

yep

pt --nogroup something

gives a lot of results in a console

[mhinz]

Could you paste the output? I wonder if it's a different format than the expected one. It should look like this:

file1:12: there is something
file2:99: something rocks

[habamax]

tables.html:412:<td style="text-align: left;">12 (something to do with Clinton and maybe the '60's)</td>
tables.md:188:            (here's            (due to           (something to do
tables.tex:403:12 (something to do with Clinton and maybe the '60's)\strut

[habamax]

If I issue

 GrepperPt asdlfkjsdlfkjsldkfjal

I get a message: "No matches found"

Otherwise silence and no results (but they should be)

[habamax]

GrepperGrep, GrepperFindstr, GrepperGit works, btw

[mhinz]

Hmm, apparently Vim's async interface changed a bit. I can reproduce it on OSX as well now.

I'm looking into it.

[habamax]

Ok, thx a lot.

[mhinz]

Short update:

I'm pretty sure it's a Vim bug by now. Some jobs simply never give output. E.g. :GrepperGrep, :GrepperGit, :GrepperAg work, but :GrepperAck and :GrepperRg don't.

Here a minimal test case: https://gist.github.com/mhinz/a5d126e6c702a6ffd0347aa70c9ccb39
(You can open that file and do :so %. ag will give output, rg won't.)

[mhinz]

@chrisbra Sorry for disturbing you, but could you have a look at the minimal test case in the above post? I read vim_dev a bit, but I'm still not sure if that bug is already reported. Thanks in advance!

(If you don't have rg installed, you can use ack --noheading --column foo for cmd2 as well.)

[chrisbra]

Not sure, if this has already been mentioned, there are a couple of bugs mentioned in the todo list and in the issue tracker like vim/vim#1026
I'll look into it.

[chrisbra]

Hm, it looks like ack is still running and waiting for something...

[mhinz]

Yup, it never returns and the stdout handler is not called even once. I have no idea how async in Vim really works, so I'm rather puzzled by this. :\

But it happens for a few programs (ack, pt, ripgrep at least), so.. what do they do differently?

[mengelbrecht]

For me rg works in async mode (macOS 10.12 + Vim8) if I use
'grepprg': 'rg --no-heading --line-number --column $* .'

The . for the current directory is essential. Otherwise it does not work and it seems rg is waiting for data from stdin.

[mhinz]

@mgee Hmm, I see.. BurntSushi/ripgrep#19

[mhinz]

So, when both, Neovim's jobstart() and Vim's job_start(), use pipes by default, where's the difference?

There must be some smart code in libuv (which is used by Neovim) that isn't part of Vim's custom solution.

[chrisbra]

sounds like it. I wonder if there is something, that should be done by Vim.

[mhinz]

Actually closed by: #77