GNU bug report logs - #25209
25.1; can't delete *Shell Command Output*

Previous Next

Full log

Message #23 received at 25209 <at> debbugs.gnu.org (full text, mbox):

From: Francesco Potortì <pot <at> gnu.org>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: 25209 <at> debbugs.gnu.org
Subject: Re: bug#25209: 25.1; can't delete *Shell Command Output*
Date: Mon, 19 Dec 2016 15:41:44 +0100

>On Dez 19 2016, Andreas Schwab <schwab <at> linux-m68k.org> wrote:
>
>> On Dez 15 2016, Francesco Potortì <pot <at> gnu.org> wrote:
>>
>>> On a long-running multi-tty Emacs, at one point the *Shell Command
>>> Output* buffer refuses to go away.
>>>
>>> If I try to kill it, nothing happens, whether the current buffer is that
>>> one or any other one.  The contents of the *Shell Command Output* buffer
>>> are always visible in the minibuffer.  So, to make it unobtrusive, I
>>> need to issue an
>>>  M-! echo -n RET
>>> every time the *Shell Command Output* buffer is dirtied.
>>
>> Did you perhaps quit while the output of a shell-command was being
>> displayed, because it took too long?  In that situation Emacs can end up
>> in a state where (minibuffer-window) points to the *Shell Command
>> Output* buffer, and kill-buffer will refuse to kill the buffer.
>
>I think the problem is that vertical-motion (as called by
>display-message-or-buffer via count-screen-lines) is not properly
>protecting against quit when it temporarily modifies the window's
>buffer.

I happen to use view-line-mode, if that can be of relevance.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.