GNU bug report logs -
#1960
23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
Previous Next
Reported by: cmr.Pent <at> gmail.com
Date: Mon, 19 Jan 2009 21:30:03 UTC
Severity: normal
Done: Chong Yidong <cyd <at> stupidchicken.com>
Bug is archived. No further changes may be made.
Full log
Message #21 received at 1960 <at> emacsbugs.donarmstrong.com (full text, mbox):
> > there's probably some problem with pc-selection-mode and the way it
> > interacts with normal-erase-is-backspace.
>
> The problem is not pc-selection mode, but how Emacs does
> normal-erase-is-backspace in multi-tty situations. Here's an even
> simpler recipe, not involving pc-selection-mode or the daemon:
>
> 1. Add the following line to .emacs:
>
> (global-set-key [C-delete] 'kill-line)
>
> 2. emacs -nw -f server-start
> 3. emacsclient -c
> 4. C-h k C-backspace
>
> => <C-backspace> runs the command kill-line
This happens because:
(defun normal-erase-is-backspace-setup-frame (&optional frame)
"Set up `normal-erase-is-backspace-mode' on FRAME, if necessary."
(unless frame (setq frame (selected-frame)))
(unless (terminal-parameter nil 'normal-erase-is-backspace)
(normal-erase-is-backspace-mode
(if (if (eq normal-erase-is-backspace 'maybe)
When using "emacs -nw -f server-start" the "(unless (terminal-parameter"
test passes and `normal-erase-is-backspace' is run.
When using "emacs -f server-start" the `terminal-parameter' call returns
non-ni, so `normal-erase-is-backspace' is not run.
It seems that terminal-parameters are copied from the first frame
created...
Not sure how normal-erase-is-backspace is supposed to work...
This bug report was last modified 16 years and 178 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.