Ramel Eshed wrote:
> Any updates about this issue?
> I'm using gnome terminal 2.31.3 (which comes with RHEL6) and must set t_BE=
> to avoid the corrupted pate issue in the terminal after exiting Vim.
>
> I think that there is no reason to break old behavior, even if there is a
> workaround for that.
The support for bracketed paste was added for good reasons. That before
this many terminals that aren't actually an xterm worked fine, even when
$TERM is set to xterm, doesn't mean this will keep working forever.
The basic problem is that if a terminal isn't really an xterm, then it
can break at any time. That isn't Vim's fault. We will try to make it
work even when the user did not setup his system exactly right, but in
this case I don't see how we can detect a "bad terminal". I wish every
terminal had a way to tell us its features instead of relying on setting
$TERM correctly.
There should also be a way to separate a term response from what the
user typed. Haven't seen any progress on that, unfortunately.
--
hundred-and-one symptoms of being an internet addict:
17. You turn on your intercom when leaving the room so you can hear if new
e-mail arrives.
/// Bram Moolenaar -- [email protected] -- 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_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].
For more options, visit https://groups.google.com/d/optout.
