add following to .vimrc to fix this issue
let &t_TI = ""
let &t_TE = ""
let &t_TE = ""
On Friday, November 8, 2019 at 10:39:01 AM UTC+8, WU RUXU wrote:
I have do more test on my system, found thatvim 8.1.2193 works, vim 8.1.2195 don't works.so I found that patch is much more relative with this issue.
On Friday, November 8, 2019 at 5:57:39 AM UTC+8, Bram Moolenaar wrote:
> I have do following test on debian 10
> 1. Xterm v 350 and v330 , with vim 8.1.2267.
> CTRL P can't work as expected
> 2. Xtrem v350 and v330, with vim 8.1.2111 ,
> CTRL P can works as expected
> 3. vim 8.1.2111 and 8.1.2267 can works as expected in gnome terminal
> 4. vim 8.1.2111 and 8.1.2267 can works as expected in native framebuffer console
I just installed xterm 350 and it works fine for me. With 'noesckeys'
and with 'esckeys'.
--
It was recently discovered that research causes cancer in rats.
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/db264de5-e33c-44b8-b8d6-27fc152229a7%40googlegroups.com.
No comments:
Post a Comment