Bram Moolenaar <[email protected]> wrote: > Philip Pemberton wrote: > > > I've just solved a packaging issue on the machine, and Apt has pulled down > > Vim 8.2.1897, with the same issue. Console output below: > > > [...] > > > philpem@cheetah:~$ gvim > > [>4;m [>4;2mphilpem@cheetah:~$ gvim > > [>4;m [>4;2mphilpem@cheetah:~$ > > You probably have a shell command in your startup files. > Combined with a terminal that doesn't ignore this escape sequence > (iterm?).
The escape codes in the shell prompt has nothing to do with Vim, unless it's a shell started in vim with :terminal ? I recall that for recent vim, terminals such as xfce4-terminal and gnome-terminal (maybe others) in Ubuntu-18.04 are too old and Vim can output spurious codes on the terminal, It hapens for example when doing :!date Ubuntu-20.04 does not have this issue (newer terminals). There is a workaround: for old terminals: add the following lines at the beginning of your ~/.vimrc: " Work around spurious characters in old terminals when doing :!date set t_TE= t_TI= Regards Dominique -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_iDiiCx0LgyerNAj-_VqJMZtaO%2Bu-G2K02Vgx2Dm-fJow%40mail.gmail.com.
