Ack command does not work on Windows 10 for Neovim about ferret HOT 13 OPEN

I don't have a Windows development machine but if anybody does and cares to look into this a PR would be welcome.

from ferret.

I also get the same error on nvim on archlinux.

Neovim version is 0.3.8

from ferret.

It appears that this happens if a search is already running, and the cancel function is called

from ferret.

specifically the jobstop function is what causes the invalid argument error

from ferret.

Seeing the same error message, using nvim 0.3.8 on windows 10. rg is installed so I assume it's using that.

from ferret.

I saw there were some nvim settings to play with. Setting let g:FerretNvim=0 produces this:

from ferret.

@tmccombs @jdhao Setting let g:FerretJob=0 fixes it for me.
@wincent this plugin is beautiful.

from ferret.

Nevermind, let g:FerretJob=0 doesn't fix it. It just worked that once then breaks after that.

from ferret.

I got this issue to go away by not specifying the ferret executable in my vimrc

from ferret.

When using neovim on windows, I also experienced the ferret ack command not working as it does on unix. Interestingly, it does work fine using vim on both operating systems. In order to get it to work using neovim on windows I had to set both the variables @loshjawrence mentioned above (g:FerretJob and g:FerretNvim) to 0

let g:is_win = has('win32') || has('win64')
let g:is_nvim = has('nvim')

if g:is_win && g:is_nvim
  let g:FerretNvim = 0
  let g:FerretJob = 0
endif

Tested using the following:

• version: NVIM v0.5.0-552-g980b12edb
• os: Windows 10
• term: Powershell v5.1.17763.1007
• gui: nvim-qt

from ferret.

I had same problem with jobstop call on MacOS 10.4, nvim 0.5.0.
Changing argument from
call jobstop(l:job)
to
call jobstop(str2nr(l:job, 10))
helped me.

I don't know if it a proper solution (I'm really bad in vimscript), but if so, I can make a PR.

from ferret.

This happens on MacOS Catalina 10.15.7, nvim 0.4.4, python 3.9.5. And the suggested solutions do not work :(

from ferret.

@mhoonjeon there is another issue with a similar symptom caused by an upgrade of rg #78 maybe some of the workarounds can help.

from ferret.