This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 19 July 2012 16:37, Ryan Johnson wrote:... and then those get encoded with utf-8 as appropriate. Got it.Hi all (mostly Andy),
I notice that mintty 1.1 handles certain key combinations differently than xterm:
ctrl+enter produces 0x1e (RS) vs. CR in xterm alt+enter produces ESC CR vs. nothing at all in xterm
ctrl+shift+<letter> emits the unicode C2 control codepoints (0xc281 through 0xc29a); xterm emits the C0 control value as if shift were unpressed.
So, two questions: 1. Is there a particular reason for this behavior?Yes, I tried to make as many key combinations as reasonably possible available to applications without having to enable a special mode. I chose ^^ (0x1e) for Ctrl+Enter rather than a multi-character code so as to be able to use it in stty settings. Similarly, Ctrl+Backspace sends ^_ (0x1f).
Fair enough. They seem like reasonable choices, especially compared with xterm (where some key combos send nothing at all!)Perhaps rxvt or some other non-xterm terminal emulator does it?Nope, they're mintty-specific.
Nice. I didn't know that was there. How hard would it be for me to get ncurses to grok these codes?
Yep:2. Is there documentation somewhere of what convention mintty follows for the various special cases?
http://code.google.com/p/mintty/wiki/Keycodes#Ctrl http://code.google.com/p/mintty/wiki/Keycodes#Special_keys
See also this on how those keycodes could be put to use in the stty settings:
http://code.google.com/p/mintty/wiki/Tips#Terminal_line_settings
... except neither mode makes any visible difference in xterm-281-1: shift+enter and ctrl+enter both continue sending CR, and alt+enter still does nothing (level 1); ctrl+a still sends ^A. Mintty works as advertized on both counts, yet another reason to like mintty, I guess.(these questions are partly triggered by frustration at shift+enter not working, which lead to me finding a reasonably sane proposal to fix these kinds of terminal woes [1]; I was surprised to find that mintty can already distinguish some key presses that xterm can't)
[1] www.leonerd.org.uk/hacks/fixterms/Hmm, that basically describes xterm's "modifyOtherKeys" mode, which mintty supports too. This can be enabled with the sequence "\e[>4;1m". (That's for level 1. There's also level 2, enabled with "\e[>4;2m", where the suggested CSI u keycodes are sent even for Ctrl+letter combinations.)
Thanks, Ryan
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |