From: "Francesco Potortì" <pot@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 25209@debbugs.gnu.org
Subject: bug#25209: 25.1; can't delete *Shell Command Output*
Date: Mon, 19 Dec 2016 15:41:44 +0100 [thread overview]
Message-ID: <E1cIz8K-0007EK-SR@tucano.isti.cnr.it> (raw)
In-Reply-To: <87eg14806a.fsf@linux-m68k.org>
>On Dez 19 2016, Andreas Schwab <schwab@linux-m68k.org> wrote:
>
>> On Dez 15 2016, Francesco Potortì <pot@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.
next prev parent reply other threads:[~2016-12-19 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:34 bug#25209: 25.1; can't delete *Shell Command Output* Francesco Potortì
2016-12-16 8:39 ` Eli Zaretskii
2016-12-19 12:45 ` Francesco Potortì
2016-12-19 16:25 ` Eli Zaretskii
2016-12-19 14:15 ` Andreas Schwab
2016-12-19 14:26 ` Andreas Schwab
2016-12-19 14:41 ` Francesco Potortì [this message]
2016-12-19 16:59 ` Eli Zaretskii
2016-12-19 22:19 ` Andreas Schwab
2016-12-19 14:27 ` Francesco Potortì
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1cIz8K-0007EK-SR@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=25209@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).