* Re: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
@ 2009-01-20 3:40 Chong Yidong
2009-01-20 16:18 ` Dan Nicolaescu
2009-01-20 16:18 ` Dan Nicolaescu
0 siblings, 2 replies; 7+ messages in thread
From: Chong Yidong @ 2009-01-20 3:40 UTC (permalink / raw)
To: emacs-devel; +Cc: pent, rfrancoise, 1960
Simplified recipe for bug#1960:
1. Put (pc-selection-mode 1) in .emacs
2. emacs --daemon
3. emacsclient -c
4. C-h k C-backspace
<C-backspace> runs the command kill-line, which is an interactive
compiled Lisp function in `simple.el'.
5. C-x C-c
6. emacsclient -c
7. C-h k C-backspace
<C-backspace> runs the command backward-kill-word, which is an
interactive compiled Lisp function in `simple.el'.
PC-selection mode binds [C-delete] to kill-line. My guess is that some
code for distinguishing delete from DEL isn't run when Emacs is started
as a daemon. It's only run sometime after the first client frame is
created, which is why C-backspace works properly for the second client
frame.
Could someone take a closer look?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-20 3:40 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace Chong Yidong
@ 2009-01-20 16:18 ` Dan Nicolaescu
2009-01-21 16:02 ` Chong Yidong
2009-01-21 16:02 ` bug#1960: " Chong Yidong
2009-01-20 16:18 ` Dan Nicolaescu
1 sibling, 2 replies; 7+ messages in thread
From: Dan Nicolaescu @ 2009-01-20 16:18 UTC (permalink / raw)
To: Chong Yidong; +Cc: pent, rfrancoise, 1960, emacs-devel
Chong Yidong <cyd@stupidchicken.com> writes:
> Simplified recipe for bug#1960:
>
> 1. Put (pc-selection-mode 1) in .emacs
> 2. emacs --daemon
> 3. emacsclient -c
> 4. C-h k C-backspace
>
> <C-backspace> runs the command kill-line, which is an interactive
> compiled Lisp function in `simple.el'.
>
> 5. C-x C-c
> 6. emacsclient -c
> 7. C-h k C-backspace
>
> <C-backspace> runs the command backward-kill-word, which is an
> interactive compiled Lisp function in `simple.el'.
What happens when repeating steps 5,6 and 7?
I am guessing that the <C-backspace> binding would toggle between
kill-line and backward-kill-word.
If that's indeed the case, then there's probably some problem with
pc-selection-mode and the way it interacts with
normal-erase-is-backspace.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-20 16:18 ` Dan Nicolaescu
@ 2009-01-21 16:02 ` Chong Yidong
2009-01-22 6:21 ` bug#1960: " Dan Nicolaescu
2009-01-22 6:21 ` Dan Nicolaescu
2009-01-21 16:02 ` bug#1960: " Chong Yidong
1 sibling, 2 replies; 7+ messages in thread
From: Chong Yidong @ 2009-01-21 16:02 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: pent, rfrancoise, 1960, emacs-devel
Dan Nicolaescu <dann@tensilica.com> writes:
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread* bug#1960: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-21 16:02 ` Chong Yidong
@ 2009-01-22 6:21 ` Dan Nicolaescu
2009-01-22 6:21 ` Dan Nicolaescu
1 sibling, 0 replies; 7+ messages in thread
From: Dan Nicolaescu @ 2009-01-22 6:21 UTC (permalink / raw)
To: Chong Yidong; +Cc: pent, rfrancoise, 1960, emacs-devel
> > 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...
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-21 16:02 ` Chong Yidong
2009-01-22 6:21 ` bug#1960: " Dan Nicolaescu
@ 2009-01-22 6:21 ` Dan Nicolaescu
1 sibling, 0 replies; 7+ messages in thread
From: Dan Nicolaescu @ 2009-01-22 6:21 UTC (permalink / raw)
To: Chong Yidong; +Cc: pent, rfrancoise, 1960, emacs-devel
> > 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...
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1960: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-20 16:18 ` Dan Nicolaescu
2009-01-21 16:02 ` Chong Yidong
@ 2009-01-21 16:02 ` Chong Yidong
1 sibling, 0 replies; 7+ messages in thread
From: Chong Yidong @ 2009-01-21 16:02 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: pent, rfrancoise, 1960, emacs-devel
Dan Nicolaescu <dann@tensilica.com> writes:
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1960: 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace
2009-01-20 3:40 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace Chong Yidong
2009-01-20 16:18 ` Dan Nicolaescu
@ 2009-01-20 16:18 ` Dan Nicolaescu
1 sibling, 0 replies; 7+ messages in thread
From: Dan Nicolaescu @ 2009-01-20 16:18 UTC (permalink / raw)
To: Chong Yidong; +Cc: pent, rfrancoise, 1960, emacs-devel
Chong Yidong <cyd@stupidchicken.com> writes:
> Simplified recipe for bug#1960:
>
> 1. Put (pc-selection-mode 1) in .emacs
> 2. emacs --daemon
> 3. emacsclient -c
> 4. C-h k C-backspace
>
> <C-backspace> runs the command kill-line, which is an interactive
> compiled Lisp function in `simple.el'.
>
> 5. C-x C-c
> 6. emacsclient -c
> 7. C-h k C-backspace
>
> <C-backspace> runs the command backward-kill-word, which is an
> interactive compiled Lisp function in `simple.el'.
What happens when repeating steps 5,6 and 7?
I am guessing that the <C-backspace> binding would toggle between
kill-line and backward-kill-word.
If that's indeed the case, then there's probably some problem with
pc-selection-mode and the way it interacts with
normal-erase-is-backspace.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-01-22 6:21 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-20 3:40 23.0.60; A combination of PC Selection, Visual Lines and emacsclient redefines C-backspace Chong Yidong
2009-01-20 16:18 ` Dan Nicolaescu
2009-01-21 16:02 ` Chong Yidong
2009-01-22 6:21 ` bug#1960: " Dan Nicolaescu
2009-01-22 6:21 ` Dan Nicolaescu
2009-01-21 16:02 ` bug#1960: " Chong Yidong
2009-01-20 16:18 ` Dan Nicolaescu
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.