Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org:
Please, Guys. Let's get NOT get emotional about this please! (It
must
be the spring air. There is even an endiannes flamewar on linux-kernel).
Well, Spring was starting to come here in Japan and then the past few
days it has returned to Winter. Maybe that's it.
SL> right of the keyboard and getting help sucks. I think we should be
SL> conservative about it and leave the setting as it is in 21.0. It is a
SL> lot safer, IMO.
Personally i think we have been conservative about it way too long.
We
really should have done it for 21.0 because we had a good reason then:
The NT port (which is a good justification) and a major version
number increase.
That's a good reason. I reject and continue to reject pleas to
emotion. Make me *want* to change it by convincing me logically and
we'll do it for 21.0, even now, days before release.
The argument _against_ doing it in 21.0 (and maybe 20.4) is that the
tty-erase-char stuff has not been tried in the field yet.
That's not a good excuse, it's not an excuse I would consider
acceptable, and it's not an excuse I'm citing.
Anyway, Steve, How come it is broken for you? This is the code that
is
used
(defsubst delete-forward-p ()
(and delete-key-deletes-forward
(or (not (eq (device-type) 'x))
(x-keysym-on-keyboard-sans-modifiers-p 'backspace))))
There are keyboards that can fake this code out. I consider it every
bit as broken for the Big Key on the upper right side of the keyboard
to not delete backwards as to enter the help subsystem.
So apparently XEmacs thinks that on your keyboard Backspace can be
generated without a modifier and thus that it is safe to change the
keyboard. This is not a question of defaults. This looks like a real bug.
Perhaps. Someone fix it if you want this patch in.
P.S. Let's all remember that set-mark-command is also bound to a
key
which can be close to impossible to generate. Can you say 'telnet.exe'?
`telnet.exe'? We removed VMS support well over a year ago. What do
you mean?
P.S.
set-mark-command was bound to Control Shift 2 on the AT&T Unix PC keyboard
and I survived. Having *anything* wrong with delete-backward-char is
unacceptable.