akiyosi

@damanis Here is a follow-up report on the survey results. I have identified the neovim commit where this problem began to occur as https://github.com/neovim/neovim/commit/1d16bba4d8b8b648d2dabd610924bcf3051a0f29. I have also identified the code...

@Karthik-Dulam @gmankab Hi, Sorry I haven't responded. By default, goneovim references `./runtime/doc/goneovim.txt` directory that exists within the directory where its own executable binaries reside. The cause of the problem could...

What is the directory structure where the goneovim binaries are located?

It may not be a direct solution, but I am thinking of allowing the environment variable `$GONEOVIM_RUNTIME` to control the runtime path where the help files reside.

@gmankab I have improved the doc detection process for goneovim. I would appreciate your feedback. https://github.com/akiyosi/goneovim/actions/runs/5033064055

I thought we could check by replacing only the goneovim binary, keeping the structure of the goneovim installed in the AUR. Nevertheless, I understand. I will merge the changes then...

@gmankab Thanks! Sorry, there was a mistake in the fix code. I have fixed it and would appreciate it if you could check it again. https://github.com/akiyosi/goneovim/actions/runs/5035731712 I would also appreciate...

@gmankab Oops, sorry, the root was missing from the path. Fixed again. https://github.com/akiyosi/goneovim/actions/runs/5037936317

Ummm, In parallel I had also created an environment to check the operation, but if `/usr/share/nvim/runtime`is not included in runtimepath, it is not possible to see the help. This is...

@gmankab Thanks for confirming. Yes, it is because the path (`/usr/share/nvim/runtime`) is not include in the runtimepath of nvim