From: Paul Griepentrog <pgriepen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Adrian Robert <adrian.b.robert@gmail.com>, 6616@debbugs.gnu.org
Subject: bug#6616: S-TAB is mismapped in the *Help* buffer
Date: Mon, 12 Jul 2010 22:42:14 -0700 [thread overview]
Message-ID: <4C3BFCB6.8000002@gmail.com> (raw)
In-Reply-To: <83mxtwsei9.fsf@gnu.org>
Thanks for looking into this.
On 7/12/10 12:10 PM, Eli Zaretskii wrote:
> > From: Adrian Robert <adrian.b.robert@gmail.com>
> > Date: Mon, 12 Jul 2010 22:03:11 +0300
> > Cc: Paul Griepentrog <pgriepen@gmail.com>,
> > 6616@debbugs.gnu.org
> >
> >
> > These lines were in the file when I started working with the port (more
> > than 2 years ago ;), and although the definitions got moved around
> > slightly, I never removed anything unless a problem was reported.
Now that
> > we have this report, I propose removing BOTH of the S-tab lines. I tried
> > this locally and it did no harm, and let S-tab be interpreted (though
some
> > default mapping seems to translate it to plain tab).
With the proposed change there still is no binding for backward-button in
*Help* and many other modes... the real problem. The translation from S-TAB
to TAB effectively drops the shift modifier.
How about removing:
(put 'S-tab 'ascii-character (logior 16 ?\t))
and binding [S-tab] to [backtab] in the `ns-alternatives-map' instead?
(define-key map [S-tab] [backtab])
Maybe stretching it here, but along this line of thinking, is it useful to
distinguish between [S-tab] and [backtab]? Bug #1281 points out that it
becomes a hassle for users -- at least under Windows OS -- who must rebind
both [S-tab] and [backtab].
If it is not useful, we could remove the duplicate bindings which several
modes provide. These modes often bind a combination of [S-tab], "\M-\t" or
"\e\t" to the same function invoked by [backtab]:
- forms
- info
- widget
- org-table
- org
- mh-letter
- mh-folder
- mh-show
- info
Instead we could align it to other modes which only use [backtab]
- erc
- grep
- compile
- ses
- diff-mode
- log-view
Thanks for the consideration.
> Sure, go ahead and remove these lines, and please close the bug after
> you do.
>
> Thanks.
next prev parent reply other threads:[~2010-07-13 5:42 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3BFCB6.8000002@gmail.com \
--to=pgriepen@gmail.com \
--cc=6616@debbugs.gnu.org \
--cc=adrian.b.robert@gmail.com \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.