Closed GoogleCodeExporter closed 8 years ago
What's your use case?
Those control codes are already available through the appropriate Ctrl+symbol
combinations such as Ctrl+], and also through special keys or combinations such
as Pause or Ctrl+Enter, as documented at
http://code.google.com/p/mintty/wiki/Keycodes.
The Ctrl+digit combinations are rather non-obvious compared to the Ctrl+symbol
ones, so I'd decided that it would be more useful to assign them different key
codes to allow them to be told apart.
Original comment by andy.koppe
on 17 Nov 2012 at 6:18
Proposed change would add compatibility with other terminals like putty and
xterm. ctrl+digit may be non-obvious but they are still used but other software.
"Those control codes are already available through the appropriate"
IMHO well known keyboard layouts shouldn't be changed without good reasons.
"Ctrl+symbol combinations such as Ctrl+]"
There is NO [ and ] keys in my keyboard.
Use case:
Is it really needed? Compatibility should be enough.
Offtopic:
And ATM ^7 emits 0x1f instead of ^[[1;mx and ^0 doesn't work at all.
Original comment by jik...@gmail.com
on 19 Nov 2012 at 4:16
To be clear: I was quite aware what xterm does here when deciding that being
able to distinguish those Ctrl+digit combinations from corresponding
Ctrl+Symbol ones would be more useful. That might well have been wrong, but
yes, it is going to take more than citing compatibility to convince me.
What's your keyboard layout?
The Ctrl+symbol logic implicitly tries adding Shift to see whether that yields
a symbol corresponding to a control character, so Shift+7 presumably yields '_'
or '/' on your layout.
If you're on something like the German layout, where AltGr+8 yields '[', then
Ctrl+AltGr+8 will get you ^[.
Original comment by andy.koppe
on 1 Dec 2012 at 7:01
I forgot to say, Ctrl+zero resets the font size, whereas Ctrl+plus and
Ctrl+minus increment and decrement it, respectively. That can be disabled on
the Keys page of the options.
Original comment by andy.koppe
on 2 Dec 2012 at 6:37
Original comment by andy.koppe
on 3 Jan 2013 at 11:00
Original issue reported on code.google.com by
jik...@gmail.com
on 24 Oct 2012 at 2:18