Lucas Hoffmann

I think this question goes to @scheibler. If you have special compatibility problems I am open to PRs, preferably RFC conforming stuff.

I do not remember much from when the original fix was merged. Looking at the code it seems that the generator that produces the thread ids might produce an invalid...

This should not close #35 as it does not provide a way to specify an alternate pass executable but just replaces the default eecutable.

This is not possible with the current design of nvimpager: In pager mode nvim is started normally with a TUI, in cat mode nvim is started with the `--headless` flag....

Maybe this is related to #99 and #101: with version 0.10 neovim changed the default color scheme and I noticed that some colorschemes did implicitly assume some different default colors...

If by bob you mean https://github.com/MordechaiHadad/bob I don't know it. Nvimpager does not bother where you put neovim or how you install it. It does however require the command line...

Your last comment is not very helpful. You are actually not calling nvimpager yourself. You are calling man. If you read the man page of man itself you will learn...

Maybe bob inspects the argv0 of the command that is executed like snap does. Compare the the problems in #82. Can you check if the nvim versions installed by bob...

I tried to do it with `:term` a long while ago but was not successful. My experiments are documented here: https://vi.stackexchange.com/questions/16624/use-terminal-to-display-file-with-ansi-escape-codes The two problems I had were: 1. I can...

Some tests depend on the default colorscheme of nvim and that changed between 0.9 and 0.10. I have now added code to deactivate these tests in the flake and in...