On Mon, Jan 8, 2018 at 7:42 AM, Kazunobu Kuriyama <[email protected]> wrote: > Sorry, I already tried reproducing the issue a few days ago and, as what I > got was a bit different from what the OP reported (at least in appearance), > I had been in wait-and-see mode since then (Actually, I've been busy > recently :) > > What I got was as follows: For all the GUIs running on X11, namely, Athena, > Motif, GTK+ 2 and 3, they couldn't distinguish <S-Esc> from <Esc> when they > were launched with gvim -u NONE, but they did with gvim -u NONE -N. > > Interestingly, MacVim showed the same behavior (gvim was replaced with mvim > when I launched it from the command line). > > Summing up, I concluded that, with non-compatible mode at least, all the > GUIs for UNIX-like systems are able to "map <S-Esc> separately from <Esc>". > > So I cannot be sure if the issue is a bug of Vim or not.
When I start gvim (Huge version 8.0.1428 with GTK2-GNOME GUI) with -u NONE -U (and the package xorg-x11-server being at version 7.6_1.18.3-28.1, and libxcb1 and libxcb-devel at version 1.11.1-6.1, as distributed as part of openSUSE Leap 42.3 with all updates applied), then start Insert mode and hit Ctrl-V followed by Shift-Esc, what is inserted (as seen by going back to Normal mode and hitting ga) is a plain Esc but this is not necessarily a bug. Vim intentionally does not distinguish between Ctrl-a and Ctrl-Shift-a, Ctrl-b and Ctrl-Shift-b, etc., and (Ctrl + printable key) where the "printable key" is other than A-Z, a-z, @, [, \, ], ^, _, ? usually either gives nothing or ignores the Ctrl modifier. This is a legacy from ASCII where those combinations were used for 0x00 to 0x3F plus 0x7F (a total of 33 values i.e. 26+7) and where the difference between upper- and lower-case was intentionaly neutralized in the presence of Ctrl. Legacy vi followed ASCII in that regard and you know (or should know) how Bram is attached to upward compatibility. In Console Vim the results are even less reproducible since in that case there is an additional layer (the console or console emulator) between the keyboard and Vim. Best regards, Tony. -- -- 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.
