Juri Linkov [EMAIL PROTECTED] writes:
One way to fix this bug is to replace the following line in
`shell-filter-ctrl-a-ctrl-b':
(goto-char (or comint-last-output-start (point-min)))
with
(goto-char (or (and (marker-position comint-last-output-start)
Romain Francoise wrote:
Juri Linkov [EMAIL PROTECTED] writes:
One way to fix this bug is to replace the following line in
`shell-filter-ctrl-a-ctrl-b':
(goto-char (or comint-last-output-start (point-min)))
with
(goto-char (or (and (marker-position comint-last-output-start)
One way to fix this bug is to replace the following line in
`shell-filter-ctrl-a-ctrl-b':
(goto-char (or comint-last-output-start (point-min)))
with
(goto-char (or (and (marker-position comint-last-output-start)
comint-last-output-start)
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
* Start an async shell command: M-! sleep 100 RET
* Switch to the buffer *Async Shell Command*
* Type C-c C-c
I got the error: Marker does not point anywhere
Backtrace looks as follows:
Debugger
* Start an async shell command: M-! sleep 100 RET
* Switch to the buffer *Async Shell Command*
* Type C-c C-c
I got the error: Marker does not point anywhere
Backtrace looks as follows:
Debugger entered--Lisp error: (error Marker does not point anywhere)
shell-filter-ctrl-a-ctrl-b()