2

Good day!

Do yo have any idea how to fix this issue? Please refer to the screenshot. enter image description here

I don't have the slightest clue why these characters are appearing. My vim-fugitive plugin was working fine before.

Thanks in advance!

Martin Tournoij
  • 62,054
  • 25
  • 192
  • 271
Oneb
  • 21
  • 2
  • 1
    What is your terminal? Have you tried it in another one, say, Konsole, Gnome terminal, Xterm or Alacritty? GVim? – Maxim Kim Aug 23 '20 at 09:02
  • Font issue most likely. Or encoding maybe – D. Ben Knoble Aug 23 '20 at 13:57
  • Looks like the symbol some apps show when a font doesn't have a representation for a particular Unicode character. The number in the box is the code point, I think. – B Layer Aug 23 '20 at 21:50
  • The character in the box is 001B, which is ESC. These are terminal escape sequences: ESC [ >4;2m (the > is somewhat unusual here, ESC [ n m for a number n or sequence of numbers separated by semicolon is to set colors and attributes IIRC.) – filbranden Aug 24 '20 at 01:30
  • Where's the the [? Do you think that's it overlapping with the 001B glyph? Without the [ it's not color codes. Either it signals beginning of ansi mode or it's "set numeric keypad mode" from what I can tell. Even with [ I don't think it is color. 1B 5B 3E is ... "set current keyboard language"? ... hmm. – B Layer Aug 24 '20 at 09:35
  • My eyes glazed over reading an old terminal sequence manual so I welcome someone else to look. :D – B Layer Aug 24 '20 at 09:44
  • @MaximKim I am using i3-sensible-terminal. The default which comes out of the box for i3. No, I haven't tried it with other terminals. – Oneb Aug 24 '20 at 12:59
  • @Oneb i3-sensible-terminal is just a wrapper to run a terminal program... I'm guessing you have something like urxvt or similar... Maybe use ps to figure it out? What is $TERM set to (in the shell)? – filbranden Aug 25 '20 at 03:13
  • @BLayer Yeah the [ is superposed, if you look closely at the right side of the square around the Unicode for ESC you'll see the [ there... These are almost surely terminal escape sequences, but the > looks unusual there, might be what is causing the issue... – filbranden Aug 25 '20 at 03:15
  • 1
    @filbranden Since learning that the code point is 001B I've been 99% sure it's ANSI escape sequences and if there's really a [ in there, which seems to be the case, a CSI sequence, in particular. I've just questioned whether they are color-related. It depends on whether the > is an error or not. If not, then I think it has to be a non-color control sequence. Knowing for sure about the > would be nice but it might be more productive to attack this from a different angle. (Like trying a different terminal, for one.) – B Layer Aug 25 '20 at 03:33
  • Good day! I'll try to use a different terminal and keep you guys posted asap. Just been busy for past couple of days. – Oneb Aug 25 '20 at 13:05
  • 1
    Another sighting What's t_TE and t_TI added by vim 8? (confirmed by author as same issue). – B Layer Sep 21 '20 at 10:41
  • 1
    As advised in :h modifyOtherKeys, simply :let &t_TE='' | let &t_TI='' should help. – Matt Sep 21 '20 at 12:03

0 Answers0