unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
	"'Paul Griepentrog'" <pgriepen@gmail.com>
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, 1 Aug 2010 07:24:06 -0700	[thread overview]
Message-ID: <75F343B7B5464F16B7E14D0F0E18BC5F@us.oracle.com> (raw)
In-Reply-To: <jwvr5ij8aic.fsf-monnier+emacs@gnu.org>

> > 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.

I disagree.  S-TAB has always been a free global key, and it has remained free
in most keymaps.

In Emacs there are several different behaviors that here and there are
associated with TAB.  The use of TAB for navigation in the sense of being
opposite to [backtab] (e.g. navigation in Info or *Help*) is only one of them,
and it is a fairly minor one (for Emacs).  We only recently added it to Info.
Arguably it can be said to make sense for other, similar read-only modes such as
*Help*.  Beyond that it does not necessarily make sense.

Please do not bind S-TAB in a general way to [backtab] or anything else.  Modes
that really need that can do so.  That leaves other code (e.g. other modes, user
code, 3rd-party code) free to use S-TAB for other uses, especially uses that are
related to a particular use of TAB.  TAB for navigation is only one use of TAB.

We already have potential and some real conflicts between different meanings of
TAB.  A mode needs to choose which meaning it prefers when there is a potential
conflict.  Some modes try to combine such behaviors into a DWIM behavior.  This
is enough - let's not make this more problematic by throwing S-TAB into the mix
in a predefined way.  Let the code in question decide.

Bind S-TAB to `backtab' for *Help* if you want - that's helpful.  Likewise
perhaps some view-mode contexts (maybe all of them; dunno).  But otherwise
please leave it alone.  Thx.







  reply	other threads:[~2010-08-01 14:24 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 [this message]
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
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=75F343B7B5464F16B7E14D0F0E18BC5F@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=6616@debbugs.gnu.org \
    --cc=adrian.b.robert@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=pgriepen@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).