unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "dickey" <dickey@his.com>
Subject: Re: How to make <shift> work with <control> in xterm?
Date: 14 Oct 2006 05:05:31 -0700	[thread overview]
Message-ID: <1160827531.924082.215970@i3g2000cwc.googlegroups.com> (raw)
In-Reply-To: <87y7rj8mig.fsf@thalassa.informatimago.com>

Pascal Bourguignon wrote:
> id.brep@gmail.com writes:
> > I use xterm, I think it's graphical terminal, is it possibleto make
> > <shit>
> > work with <control> in xterm?
>
> Not AFAIK.
>
> The question is that there is no line protocol to encode shit+control+key.

xterm has an experimental feature for this (three levels, where the
intermediate level
may change, but the third addresses this in part).  See
"modifyOtherKeys" in patches
214-216:

http://invisible-island.net/xterm/xterm.log.html

  parent reply	other threads:[~2006-10-14 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  5:01 How to make <shift> work with <control> in xterm? id.brep
2006-10-14  6:00 ` Pascal Bourguignon
2006-10-14  8:43   ` id.brep
2006-10-14 12:05   ` dickey [this message]
2006-10-14  7:06 ` Harald Hanche-Olsen
2006-10-14 18:40 ` Ilya Zakharevich

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=1160827531.924082.215970@i3g2000cwc.googlegroups.com \
    --to=dickey@his.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.
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).