some flaky chars in NayvyImportsFzF about vim-nayvy HOT 10 CLOSED

there is flaky I when/in NayvyTestGenerateFZF too.

from vim-nayvy.

@Shane-XB-Qian

Could you please check whether or not followings fix the problem

• Rxecute in shell echo $FZF_DEFAULT_OPTS
• If --ansi option is not there, add --ansi in $FZF_DEFAULT_OPTS
• Run NayvyImportsFzF again

from vim-nayvy.

• If --ansi option is not there, add --ansi in $FZF_DEFAULT_OPTS

ok, thanks, yes, so looks this only recogonize ansi palettes

from vim-nayvy.

2. the init I do not understand where is it from.

how about this one? why there is an init I char?

from vim-nayvy.

• If --ansi option is not there, add --ansi in $FZF_DEFAULT_OPTS

ok, thanks, yes, so looks this only recogonize ansi palettes

umm..., I don't have any idea why.
nayvy just prints ansi palettes escape sequences to the standard output and pass thme to fzf.

If colored output is not necessary, just tweks the flag (see following link) will fix the problem.

from vim-nayvy.

2. the init I do not understand where is it from.

how about this one? why there is an init I char?

I cannot reproduce this problem also, and have no idea about it 😢

from vim-nayvy.

something like here? it had a strange I ahead.
// "autmux/nayvy_import_fzf_scenario.yml" line 30

from vim-nayvy.

@Shane-XB-Qian

Unfortunately no, this script is just a configuration file for automatically producing the GIF.
And, insertion of I is not repdoducible for me, so this is some environment-specific problem.

from vim-nayvy.

Unfortunately no, this script is just a configuration file for automatically producing the GIF.

i was just doing a guess:
maybe similar there some kinds of keystrokes somewhere, it should be an input char but not sure where generated it.

from vim-nayvy.

anyway, it is a problem when/if integ with fzf.
let it be..

from vim-nayvy.