unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 19 Dec 2016 18:25:51 +0200	[thread overview]
Message-ID: <83zijr51io.fsf@gnu.org> (raw)
In-Reply-To: <E1cIxKG-0001zK-P9@tucano.isti.cnr.it> (message from Francesco Potortì on Mon, 19 Dec 2016 13:45:56 +0100)

> Date: Mon, 19 Dec 2016 13:45:56 +0100
> From: Francesco Potortì <pot@gnu.org>
> Cc: 25209@debbugs.gnu.org
> 
> >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.
> 
> Unfortunately I had already tried all your suggestions.  I had not
> thought about the hooks, but now that I look at them I would say that I
> have not set them myself and they look like standard ones.

I have no doubt that you (or some code in Emacs) somehow caused the
shell output buffer to be displayed in the minibuffer.  Emacs refuses
to kill such buffers, and that's what you see.

> I can obviously disregard this, kill Emacs and start a fresh one, but
> maybe there is a bug lurking somewhere and this is a unique chance to
> hunt it down :)

If there's a bug that causes this, it has done its thing long ago, and
our chances to hunt it down given your situation are pretty much nil.

Thanks.





  reply	other threads:[~2016-12-19 16:25 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 [this message]
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

  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=83zijr51io.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 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).