unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Bind right shift and TAB won't work
Date: Sun, 12 May 2013 10:53:39 +0200	[thread overview]
Message-ID: <7EE36103-BE78-42D1-AFA8-4359B95167B4@Web.DE> (raw)
In-Reply-To: <87k3n5dw7z.fsf@VLAN-3434.student.uu.se>


Am 11.05.2013 um 23:48 schrieb Emanuel Berg:

> I tried both below approaches but behaviour suggests that Emacs
> doesn't sense the shift (or ignores it) when combined with TAB.

When you're doing this in terminal it's likely that GNU Emacs cannot see a difference.

One way to determine what GNU Emacs receives is to type in *scratch* buffer the key combinations you want to bind to keys and then invoke C-h l. This opens a new buffer which lists the input events.

--
Greetings

  Pete

Eternity is a terrible thought. I mean, where's it going to end?
				- Tom Stoppard




  parent reply	other threads:[~2013-05-12  8:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11 21:48 Bind right shift and TAB won't work Emanuel Berg
2013-05-11 22:43 ` Drew Adams
     [not found] ` <mailman.25578.1368312212.855.help-gnu-emacs@gnu.org>
2013-05-12  7:15   ` Emanuel Berg
2013-05-12 14:57     ` Peter Dyballa
2013-05-12 15:37     ` Drew Adams
     [not found]     ` <mailman.25599.1368370687.855.help-gnu-emacs@gnu.org>
2013-05-12 20:56       ` Emanuel Berg
2013-05-13  8:23         ` Bob Proulx
     [not found]     ` <mailman.25602.1368373047.855.help-gnu-emacs@gnu.org>
2013-05-12 21:23       ` Emanuel Berg
2013-05-13  5:29         ` Drew Adams
     [not found]         ` <mailman.25622.1368422975.855.help-gnu-emacs@gnu.org>
2013-05-13 16:18           ` Emanuel Berg
2013-05-12  8:53 ` Peter Dyballa [this message]
     [not found] ` <mailman.25595.1368348824.855.help-gnu-emacs@gnu.org>
2013-05-12  9:27   ` Emanuel Berg
2013-05-12 15:05     ` Peter Dyballa
     [not found]     ` <mailman.25600.1368371123.855.help-gnu-emacs@gnu.org>
2013-05-12 21:08       ` Emanuel Berg
2013-05-13  8:33         ` Bob Proulx
2013-05-13 20:50           ` oitofelix
     [not found]           ` <mailman.25684.1368478466.855.help-gnu-emacs@gnu.org>
2013-05-13 23:36             ` Emanuel Berg
2013-05-13  9:05         ` Peter Dyballa
     [not found]         ` <mailman.25626.1368434033.855.help-gnu-emacs@gnu.org>
2013-05-13 15:59           ` Emanuel Berg
     [not found]         ` <mailman.25627.1368435961.855.help-gnu-emacs@gnu.org>
2013-05-13 14:25           ` Barry Margolin
2013-05-13 16:13             ` Emanuel Berg
2013-05-13 18:09               ` Bob Proulx
2013-05-14  0:53                 ` oitofelix
     [not found]                 ` <mailman.25694.1368499364.855.help-gnu-emacs@gnu.org>
2013-05-15 14:33                   ` Emanuel Berg
2013-05-13 16:38             ` Peter Dyballa
2013-05-13 16:06           ` Emanuel Berg

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=7EE36103-BE78-42D1-AFA8-4359B95167B4@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.org \
    /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).