search

junegunn / fzf.vim

fzf :heart: vim
MIT License
9.59k stars 582 forks source link

"I" character getting inserted when calling :Files! :Buffers! #1356

Open ghost opened 2 years ago

ghost commented 2 years ago

Hello!

Could someone please help me narrow down whether this issue is coming from vim or fzf.vim? Problem description, behavior, environment setup, and steps I took listed below.

Problem

I am seeing the I character get automatically inserted when I invoke :Files! or :Buffers! command. Even in this minimal configuration, the bug occured : vim -Nu <(curl https://gist.githubusercontent.com/junegunn/6936bf79fedd3a079aeb1dd2f3c81ef5/raw) I'm launching vim in Gnome Terminal version 3.40.3 (Using VTE version 0.66.0 +BIDI +GNUTLS +ICU -SYSTEMD)

Thanks for your help !

pparidans commented 2 years ago

Actually have the same issue. Still couldn't yet figure it out...

OS: Pop!_OS 21.10 Shell: Fish 3.1.2 Terminal: GNOME Terminal 3.38.1 (Using VTE version 0.64.2 +BIDI +GNUTLS +ICU +SYSTEMD) VIM: 8.2.2434-3ubuntu3.2

Don't remember having an issue 2 weeks ago on Ubuntu 20.04 LTS. Will test it out and report it back here.

pparidans commented 2 years ago

Interesting: this issue doesn't appear using another terminal emulator (Alacritty in this case) on the same system.

@nbl- Would you mind sharing your OS/version ?

datfinesoul commented 2 years ago

I'm getting the same thing:

pparidans commented 2 years ago

Could reproduce it on Ubuntu 21.10 (which Pop!_OS 21.10 is based on). No issue on earlier versions or Debian 11 with GNOME...

ghost commented 2 years ago

Interesting: this issue doesn't appear using another terminal emulator (Alacritty in this case) on the same system.

@nbl- Would you mind sharing your OS/version ?

I'm using Void Linux.

pparidans commented 2 years ago

I'm using Void Linux.

Ok thanks for the information.

So we have different distribution (Void Linux, Pop!_OS, Ubuntu...), different shells (Fish, Bash...). Hence we are all on GNOME Terminal (but different versions). Other terminal emulators doesn't seem to exhibit this issue (tested in my case with Konsole & Alacritty).

GabrielMontplaisir commented 2 years ago

I wanted to share that I just installed fzf last night and I'm also getting this bug.

OS: Pop!_OS 22.04 5.17.5-76051705-generic Shell: bash 5.1.16 GNOME: GNOME 42.0 Terminal: Version 3.44.0 for GNOME 42 Using VTE version 0.68.0 +BIDI +GNUTLS +ICU +SYSTEMD VIM: Vi IMproved 8.2 (2019 Dec 12, compiled Apr 18 2022 19:26:30)

pbnj commented 1 year ago

I am experiencing the same bug on macOS 12.6 + fzf v0.34.0.

I noticed it happens only in tmux. Outside of tmux, there is no I character inserted in fzf prompt when I execute :Files!.

After this observation, I tried starting a new tmux session and was not able to replicate it. Seems environmental at this point, but I cannot figure out what is causing it (e.g. terminal emulator? shell session?).

pbnj commented 1 year ago

The issue appears to be intermittent only in tmux, regardless of the terminal emulator (tried iTerm2, default macOS Terminal.app, and alacritty).

Through process of elimination, I have narrowed it down to set-option -g default-terminal 'xterm-256color' in my ~/.tmux.conf (which fixes some vim + terminal 256 color issues).

My terminal emulators set TERM to xterm-256color. :Files! works fine outside of tmux with this TERM configuration, but running :Files! inside tmux with set-option -g default-terminal 'xterm-256color' results in I getting inserted in fzf prompt.

Removing this tmux option or setting it to something else (e.g. screen or tmux per tmux manpages) and restarting tmux resolves the issue for me (but obviously has other implications with vim colors not showing correctly).

trappmartin commented 4 months ago

+1, in my case set-option -g default-terminal 'xterm-256color' was injected from tmux-sensible.