search

lucc / nvimpager

Use nvim as a pager to view manpages, diffs, etc with nvim's syntax highlighting
Other
372 stars 20 forks source link

Escape sequences not translated #7

Closed ix- closed 6 years ago

ix- commented 6 years ago

Not sure, if it's really nvimpager at fault here but I tested it with PAGER set to nvimpager and less: nvimpager_vs_less

Both show numpy's mean docstring in ipython, left with nvimpager, right with less.

The same happens to man pages, if MANPAGER is set to nvimpager :

nvimpager_vs_less_man

This is using suckless' simple terminal (st), but I tested it also with xterm, same result. It is perfecly possible that there is some issue with my setup, but since I cannot find a remedy online, I reported this here in the hope that someone has a clue what's going on.

ix- commented 6 years ago

If it's relevant to anyone:

Edit: removed mistaken reference to issue 2 (Support for colors (eg with git)?) above. However, I tried the same as suggested there, git log --color | nvimpager and again, the color sequences are visible instead of the text being displayed in that color. git log --color | less displays the colors as intended. git log --color | nvimpager |less also displays the colors as intended.

lucc commented 6 years ago

I can not reproduce this right away. What version of nvimpager are you running? Also what happens if you try without an nvimpager init.vim file?

ix- commented 6 years ago

I do not have anything in .config/nvimpager/init.vim.


nvimpager -v
NVIM v0.3.0
Build type: Release
LuaJIT 2.0.4
Compilation: /usr/bin/x86_64-pc-linux-gnu-gcc -march=corei7 -O2 -pipe -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/var/tmp/portage/app-editors/neovim-0.3.0/work/neovim-0.3.0_build/config -I/var/tmp/portage/app-editors/neovim-0.3.0/work/neovim-0.3.0/src -I/usr/include -I/var/tmp/portage/app-editors/neovim-0.3.0/work/neovim-0.3.0_build/src/nvim/auto -I/var/tmp/portage/app-editors/neovim-0.3.0/work/neovim-0.3.0_build/include
Compiled by root@project2501

Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"

   system vimrc file: "/etc/vim/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info
lucc commented 6 years ago

This looks like you are running a version before 0.1 as the version option is not handled by nvimpager but by nvim itself. Please update to a newer version.

ix- commented 6 years ago

Ok, the nvimpager comes bundled by USE flag with neovim, I'll have to make a package myself. Thanks for your help.

On 6 August 2018 17:37:29 CEST, Lucas Hoffmann notifications@github.com wrote:

This looks like you are running a version before 0.1 as the version option is not handled by nvimpager but by nvim itself. Please update to a newer version.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/lucc/nvimpager/issues/7#issuecomment-410751194

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

lucc commented 6 years ago

Where can I see the sources (the ebuild file or however that is called in gentoo/funtoo) that you used?

ix- commented 6 years ago

The ebuild of neovim-0.3.0 can be found here:

https://github.com/funtoo/editors-kit/blob/master/app-editors/neovim/neovim-0.3.0.ebuild

It pulls the neovim release from their github archive.

src_install() installs a nvimpager symlink, which seems to be part of neovim. Your code is actually not pulled, iiuc. So unless your project is not downstreamed to neovim, I might have been misled by the name and barked at the wrong tree. If that's the case, I'm very sorry for wasting your time.

On 6 August 2018 19:11:58 CEST, Lucas Hoffmann notifications@github.com wrote:

Where can I see the sources (the ebuild file or however that is called in gentoo/funtoo) that you used?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/lucc/nvimpager/issues/7#issuecomment-410781007

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

lucc commented 6 years ago

I am sorry to say that it is not my code (but the code that inspired the code that inspired me). And here I was hoping I made in into some gentoo distro :laughing:

ix- commented 6 years ago

Yeah ok, then I'll see if I can craft an ebuild, if I'm handy enough. If I succeed I'll can send a pull request, so maybe it'll be included. Thanks anyway for your prompt response! Best regards, Morris

On 6 August 2018 21:30:27 CEST, Lucas Hoffmann notifications@github.com wrote:

I am sorry to say that it is not my code (but the code that inspired the code that inspired me). And here I was hoping I made in into some gentoo distro :laughing:

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/lucc/nvimpager/issues/7#issuecomment-410826110

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.