unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Griepentrog <pgriepen@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Adrian Robert <adrian.b.robert@gmail.com>, 6616@debbugs.gnu.org
Subject: bug#6616: S-TAB is mismapped in the *Help* buffer
Date: Sun, 01 Aug 2010 10:38:01 -0700	[thread overview]
Message-ID: <4C55B0F9.1060101@gmail.com> (raw)
In-Reply-To: <jwvr5ij8aic.fsf-monnier+emacs@gnu.org>

  On 7/31/10 5:04 PM, Stefan Monnier wrote:
> > and binding [S-tab] to [backtab] in the `ns-alternatives-map' instead?
>
>  Actually, we might want to do that everywhere, rather than only in
>  x-win.el and ns-win.el.

Thinking more about the problem, I think the confusion comes from
a perfect storm of evolution:

   - The [backtab] key does not exist on modern keyboards, but
     several modes define keybindings only for [backtab].  (See
     erc, grep, compile, ses, diff-mode and log-view.)

   - But, X and Windows translate [S-tab] into [backtab], so you
     don't even notice this unless you're working on a platform/
     terminal without this mapping, for example: Mac OS X.

   - Add to that: people treat [backtab] as logically the same as
     [S-tab], even though they are different key presses when you
     have a [backtab] key.

As a developer, I would be confused.  I need to map both for my
mode to be consistent across terminals/platforms.  Several modes
do this exactly.  (See forms, info, widget, org, and mh.)

I say, pick a solution and make it consistent across the modes
shipped with Emacs.  IMHO, [S-tab] is the 'correct' binding,
since we press those actual keys.  Update all the modes using
[backtab] to use [S-tab].  Now, anybody who has a [backtab] key
can actually use it, and the rest continue with [S-tab], like
they always did.  For compatibility with external modes, we could
map [backtab] to [S-tab].

I can offer a patch to this effect.






  parent reply	other threads:[~2010-08-01 17:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12  6:20 bug#6616: S-TAB is mismapped in the *Help* buffer Paul Griepentrog
2010-07-12 17:29 ` Eli Zaretskii
2010-07-12 19:03   ` Adrian Robert
2010-07-12 19:10     ` Eli Zaretskii
2010-07-13  5:42       ` Paul Griepentrog
2010-07-13  7:28         ` Adrian Robert
2010-07-13  9:50           ` Eli Zaretskii
2010-07-13  9:49         ` Eli Zaretskii
2010-08-01  0:04         ` Stefan Monnier
2010-08-01 14:24           ` Drew Adams
2010-08-01 18:59             ` Drew Adams
2010-08-01 23:32             ` Stefan Monnier
2010-08-02  1:51               ` Drew Adams
2010-08-01 17:38           ` Paul Griepentrog [this message]
2010-08-02  0:03             ` Stefan Monnier
2010-08-02  1:57               ` Drew Adams
2010-08-02  8:22                 ` Stefan Monnier
2010-08-02  4:30               ` Paul Griepentrog
2010-07-13 10:47 ` bug#6616: Closing, checked fix in to trunk r100808 Adrian Robert

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=4C55B0F9.1060101@gmail.com \
    --to=pgriepen@gmail.com \
    --cc=6616@debbugs.gnu.org \
    --cc=adrian.b.robert@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).