From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: david.ponce@wanadoo.fr, emacs-devel@gnu.org
Subject: Re: Shift Tab should move backward in help buffers
Date: Sun, 26 Jun 2005 13:03:13 -0500 (CDT) [thread overview]
Message-ID: <200506261803.j5QI3Dv17974@raven.dms.auburn.edu> (raw)
In-Reply-To: <42BEE64C.4040405@student.lu.se> (message from Lennart Borgman on Sun, 26 Jun 2005 19:30:52 +0200)
Lennart Borgman wrote:
Luc Teirlinck wrote:
>And it would be useful to have a keybinding that works by default,
>even when not using a window system. <S-tab> does not; by default, it
>usually gets translated into <tab>, so it moves forward, not backward.
>
>
Is the problem that Emacs can not see <S-tab> on all systems?
The problem is this, form `(elisp)Character Type':
The case of a graphic character is indicated by its character code;
for example, ASCII distinguishes between the characters `a' and `A'.
But ASCII has no way to represent whether a control character is upper
case or lower case. Emacs uses the 2**25 bit to indicate that the
shift key was used in typing a control character. This distinction is
possible only when you use X terminals or other special terminals;
ordinary terminals do not report the distinction to the computer in any way.
and, from `(emacs)Named ASCII Chars':
With an ordinary ASCII terminal, there is no way to distinguish
between <TAB> and `C-i' (and likewise for other such pairs), because
the terminal sends the same character in both cases.
So, from the console and from `emacs -nw', <tab>, <S-tab>, C-i and
S-C-i are indistinguishable.
`emacs -nw' is important to people with a slow connection, because
just emacs without `-nw' over a slow connection is just way to slow to
be usable.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-06-26 18:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 13:51 Shift Tab should move backward in help buffers Lennart Borgman
2005-06-26 16:30 ` David Hunter
2005-06-26 16:55 ` David Ponce
2005-06-26 17:13 ` Luc Teirlinck
2005-06-26 17:30 ` Lennart Borgman
2005-06-26 18:03 ` Luc Teirlinck [this message]
2005-06-26 18:57 ` Andreas Schwab
2005-06-27 4:39 ` David Hunter
2005-06-27 6:16 ` Miles Bader
2005-06-28 1:03 ` David Hunter
2005-06-28 1:28 ` Miles Bader
2005-06-26 17:13 ` Lennart Borgman
2005-06-27 2:08 ` Miles Bader
2005-06-27 4:47 ` David Hunter
2005-06-26 22:42 ` Richard M. Stallman
2005-06-27 9:30 ` Jason Rumney
2005-06-27 10:00 ` Miles Bader
2005-06-28 4:16 ` Richard M. Stallman
2005-06-28 5:15 ` Miles Bader
2005-06-28 6:27 ` Stefan Monnier
2005-06-28 6:41 ` Miles Bader
2005-06-28 6:52 ` Stefan Monnier
2005-06-28 8:53 ` Andreas Schwab
2005-06-28 20:44 ` Miles Bader
2005-06-28 21:29 ` Richard M. Stallman
2005-06-28 22:39 ` Miles Bader
2005-07-02 0:23 ` David Hunter
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 6:24 David PONCE
2005-06-28 1:50 ` David Hunter
2005-06-28 8:42 LENNART BORGMAN
2005-06-28 19:42 ` Eli Zaretskii
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=200506261803.j5QI3Dv17974@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=david.ponce@wanadoo.fr \
--cc=emacs-devel@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 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).