Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: B [backspace] should act like B [delete]?
Date: 14 Jun 1999 20:44:22 -0400	[thread overview]
Message-ID: <vxkbteis36h.fsf@beaver.jprc.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "14 Jun 1999 23:57:03 +0200"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> On Emacs, <backspace> and <delete> (by default) generate the DEL ascii
> character in much the same way as <tab> generates the TAB ascii
> character.

I don't pretend to understand all the underlying goo of keyboard
handling in XEmacs, but I do undesstand that XEmacs doesn't convert
incoming X keyboard events into any charset elements.  Backspace and
Delete are just that, Backspace and Delete.  Notably, `C-h' and
Backspace are not at all the same thing.

> I don't really believe that people turn off the effect that <tab> and
> C-i are the same thing

Under X, XEmacs distinguishes between the concepts of <tab>, `C-i',
and `C-<tab>'.  There is no charset analogue to this; taken as mere
ASCII charset elements, a <tab> is already a "controllified" `I'
(which is to say, the control characters are those for which the upper
3 bits have been zeroed).

Within a terminal environment, including an xterm, XEmacs is of course
limited to the set of key events that survive xterm's massaging of the
X event stream into an ASCII stream -- `C-<tab>' is indeed identical
to <tab> is identical to `C-i'.

--karl


  reply	other threads:[~1999-06-15  0:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-14 15:27 Karl Kleinpaste
1999-06-14 16:03 ` Kai.Grossjohann
1999-06-14 16:23   ` Karl Kleinpaste
1999-06-14 21:49     ` Kai.Grossjohann
1999-06-14 17:07   ` Harry Putnam
1999-06-14 21:51     ` Kai.Grossjohann
1999-06-14 17:55   ` Hrvoje Niksic
1999-06-14 21:57     ` Kai.Grossjohann
1999-06-15  0:44       ` Karl Kleinpaste [this message]
1999-06-15 15:33       ` Hrvoje Niksic

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=vxkbteis36h.fsf@beaver.jprc.com \
    --to=karl@justresearch.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.
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 NNTP newsgroup(s).