From: Eli Zaretskii <eliz@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 25209@debbugs.gnu.org
Subject: bug#25209: 25.1; can't delete *Shell Command Output*
Date: Fri, 16 Dec 2016 10:39:58 +0200 [thread overview]
Message-ID: <83k2b08dy9.fsf@gnu.org> (raw)
In-Reply-To: <E1cHYz9-0001ux-PU@tucano.isti.cnr.it> (message from Francesco Potortì on Thu, 15 Dec 2016 17:34:23 +0100)
> Date: Thu, 15 Dec 2016 17:34:23 +0100
> From: Francesco Potortì <pot@gnu.org>
>
> 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.
>
> I am still running that Emacs, so I can try to debug something. If you
> suggest me where to look, I can do that when I have time (probably not
> it nthe next few days).
Some questions come to mind, hopefully one of them will help you:
Are you in recursive edit level, perhaps?
When the cursor is shown in that buffer in the echo area, does typing
C-g or "C-x o" get you out of that, and can you then kill that buffer?
Or maybe try "C-x b" to switch to a minibuffer in that situation.
Do you have some non-nil kill-buffer-hook, and if so, what does that
do? What about kill-buffer-query-functions -- any non-nil value for
that?
What happens if you set debug-on-error non-nil, and then try to kill
that buffer? What errors, if any, pop up, and what do they show?
When you attempt to kill the buffer, do you see any messages added to
*Messages*?
The most promising lead, IMO, is the one about this buffer being shown
in the echo area: kill-buffer won't kill the current minibuffer
buffer, so I think you should try to break that link. Thus the first
2 questions above are the most probable cause of your trouble.
next prev parent reply other threads:[~2016-12-16 8:39 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 [this message]
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ì
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k2b08dy9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25209@debbugs.gnu.org \
--cc=pot@gnu.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 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.