Skip to content
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

Disappering match count in the command line #8

Open
strboul opened this issue Jan 7, 2022 · 1 comment
Open

Disappering match count in the command line #8

strboul opened this issue Jan 7, 2022 · 1 comment

Comments

@strboul
Copy link

strboul commented Jan 7, 2022

yaml-revealer is great. However, I've realized that the match count part is missing when the tags are displayed in the command line.

The left picture is with yaml-revealer plugin on and the right one is without.

screenshot

It'd be great to keep both in the command line (at least follow the user settings instead of overwriting) or have an option to reveal the tree in a floating window.

nvim --version
NVIM v0.6.0-dev+617-g64abd7be7
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az87-534

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

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

Run :checkhealth for more info
@Einenlum
Copy link
Owner

Einenlum commented Jan 7, 2022

Oooh, nice catch, thanks!

Indeed we need to think about an alternative output then. My only issue is that I would like to keep a BC with vim 8 so that the plugin is vim/neovim compatible. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants