-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Colorizing is not consistent #103
Comments
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 and did not set them. Can you reproduce this problem with neovim 0.9 and 0.10 and also with the default colorscheme? (You can use the |
I tested on nightly before.
I tried to use bob, but somehow nvimpager doesn't work anymore using bob's installation. How do I fix? |
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 switches documented in the man page of the official neovim. Especially the -R switch as you have noticed. If bob does something strange to the command line parsing of neovim you have to figure that out first. You can find out where in nvimpager the error message comes from when running it in debug mode: |
When I invoke nvim v0.9.5 with Log: (I removed the prompt-related noise)
Weird, isn't it? |
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 that man looks at the It would be much better if you can find an example to reproduce this with nvimpager directly. If it only happens with man pages you can have man render a page for you and view it with nvimpager afterwards:
The error message
looks strange to me. It is not from nvimpager. Do you know where it comes from? |
Hm. I am sorry about a non-helpful comment. Then I don't understand either. The commands you suggest produce the same output: |
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 are symlinks or wrapper scripts (if they are symlinks then please also check recursively): ls -l /path/to/bobs/v0.9.5/nvim
file /path/to/bobs/v0.9.5/nvim What happens if you run /path/to/bobs/v0.9.5/nvim -R
exec -a foo /path/to/bobs/v0.9.5/nvim -R |
That is exactly what I did already, I manually invoked v0.9.5 with $ file .local/share/bob/nvim-bin/nvim
.local/share/bob/nvim-bin/nvim: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=adcf999f43a8b51afa6c665656cd26b9d24eda10, for GNU/Linux 4.4.0, stripped |
I have same issue
|
Hello! At first, I though this was a
github-cli
bug. So I posted there. The only important point in that issue is this comment. As you can see, the colors thatglamour
creates, are displayed correctly. However all the colors fromgh-cli
are not correct. Do you have an idea what the culprit might be? Bothless
andbat
display the correct colors in that case.The text was updated successfully, but these errors were encountered: