If A3's not a showstopper, though, maybe the best next step would be
to start a test suite, to ensure things are working the way they're
supposed to work. Plus it gives a spec to shoot for. Things to
include would definitely be these sets:
<Tab> <Ctrl-I> <Ctrl-Shift-I> ^I
<C-m> <Enter> ^M
<C-[> <Esc> ^[
<M-i> <é>
<Alt-d> <Escape-d>
I'm not entirely sure what you mean by these sets, with regard to the
caret notation at the end. What do you mean by<Ctrl-I> vs ^I ? I'm
happy that this ought to be considered against<Tab> and<Ctrl-Shift-I>
however.
I think Ben was drawing the distinction between receiving an 0x09 byte
(^I) and receiving something that was known to be Ctrl-I via CSI.
Judging from your earlier mails, the problem is not between ^I and
Ctrl-I, though, but between ^I and Tab, which even newer terminals
represent the same way, right? Nevertheless, we still have two things to
test here: the situation where Vim gets ^I and doesn't know whether it's
Ctrl-I, and the situation where Vim gets ^I and knows it can't be
Ctrl-I, because it knows Ctrl-I would have been represented by that
terminal as CSI.
Ben.
--
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
