From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 13839@debbugs.gnu.org
Cc: Victor Ren <victorhge@gmail.com>
Subject: bug#13839: xterm/mintty control sequences support when formatOtherKeys = 1
Date: Thu, 28 Feb 2013 10:42:47 -0500 [thread overview]
Message-ID: <jwvmwuojvib.fsf-monnier+emacs@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 33 bytes --]
Moving this to the bug tracker.
[-- Attachment #2: Type: message/rfc822, Size: 6126 bytes --]
From: Victor Ren <victorhge@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Cc: Ren Victor <victorhge@gmail.com>
Subject: Re: xterm/mintty control sequences support when formatOtherKeys = 1
Date: Thu, 28 Feb 2013 22:33:58 +0800
Message-ID: <83mwuopkx5.fsf@ericsson.com>
>>>>> "" == Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> For example, pressing C-0 in xterm will send control sequence
>> "\e[27;5;48~" by default, which is supported now. When
>> "formatOtherKeys" is set to 1, C-0 is sent as "\e[48;5u" which is
>> another shorter format.
>> The easiest change I can image is to define a lot of key binds
>> for those control sequence, for example, (define-key map
>> "\e[48;5u" [?\C-0])
> Y see, that looks fine. If you can prepare a patch for it, I'd
> be very happy to install it. Or can we simply take all the
> "\e[27;NN,MM~" and add a corresponding "\e[MM;NNu"? If so, I can
> write the patch myself.
Yes, I think so. Maybe this is the better way than checking terminal
capacities and then deciding to enable which format.
/Victor
> Stefan
>> On Wed, Feb 27, 2013 at 9:54 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
>>> > When setting "formatOtherKeys" resource to 1 in xterm, 'CSI u'
>>> format is > used for non-standard keycodes. This is also how
>>> mintty support > "modifyOtherKeys" by default.
>>>
>>> > But in term/xterm.el, only 'CSI 27" format is supported.
>>>
>>> > I think it is worth supporting "CSI u" format control
>>> sequences. > What do you think of adding them to
>>> teerm/xterm.el? or anyone can do it?
>>>
>>> I'm not familiar with those "CSI 27" and "CSI u" formats (the
>>> name vaguely reminds me of distant memories, but that's about
>>> it). Could give us an idea of what kind of changes to
>>> term/xterm.el that would entail?
>>>
>>>
>>> Stefan
>>>
next reply other threads:[~2013-02-28 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 15:42 Stefan Monnier [this message]
2013-02-28 16:31 ` bug#13839: xterm/mintty control sequences support when formatOtherKeys = 1 Stefan Monnier
2013-03-01 15:15 ` Ren Victor
2013-03-11 18:25 ` Stefan Monnier
2013-03-12 8:04 ` Ren Victor
2014-07-08 18:54 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvmwuojvib.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13839@debbugs.gnu.org \
--cc=victorhge@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).