From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Francesco =?UTF-8?Q?Potort=C3=AC?= Newsgroups: gmane.emacs.bugs Subject: bug#25209: 25.1; can't delete *Shell Command Output* Date: Mon, 19 Dec 2016 13:45:56 +0100 Message-ID: References: <83k2b08dy9.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Trace: blaine.gmane.org 1482151636 31018 195.159.176.226 (19 Dec 2016 12:47:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 19 Dec 2016 12:47:16 +0000 (UTC) Cc: 25209@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Dec 19 13:47:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cIxLQ-0006U8-Ci for geb-bug-gnu-emacs@m.gmane.org; Mon, 19 Dec 2016 13:47:08 +0100 Original-Received: from localhost ([::1]:45028 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIxLU-0002jL-V1 for geb-bug-gnu-emacs@m.gmane.org; Mon, 19 Dec 2016 07:47:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIxLO-0002j3-0U for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2016 07:47:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIxLK-0006Rl-30 for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2016 07:47:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59769) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cIxLJ-0006RV-VU for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2016 07:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cIxLJ-0007sz-Jx for bug-gnu-emacs@gnu.org; Mon, 19 Dec 2016 07:47:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Francesco =?UTF-8?Q?Potort=C3=AC?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 19 Dec 2016 12:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25209 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 25209-submit@debbugs.gnu.org id=B25209.148215156230229 (code B ref 25209); Mon, 19 Dec 2016 12:47:01 +0000 Original-Received: (at 25209) by debbugs.gnu.org; 19 Dec 2016 12:46:02 +0000 Original-Received: from localhost ([127.0.0.1]:46935 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cIxKM-0007rJ-Ak for submit@debbugs.gnu.org; Mon, 19 Dec 2016 07:46:02 -0500 Original-Received: from blade3.isti.cnr.it ([194.119.192.19]:26355) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cIxKK-0007r2-DF for 25209@debbugs.gnu.org; Mon, 19 Dec 2016 07:46:01 -0500 Original-Received: from tucano.isti.cnr.it ([146.48.81.102]) by mx.isti.cnr.it (PMDF V6.5-x6 #1251) with ESMTPSA id <01Q8O1NE48NGBG1XGY@mx.isti.cnr.it> for 25209@debbugs.gnu.org; Mon, 19 Dec 2016 13:45:57 +0100 (MET) Original-Received: from pot by tucano.isti.cnr.it with local (Exim 4.88) (envelope-from ) id 1cIxKG-0001zK-P9; Mon, 19 Dec 2016 13:45:56 +0100 In-reply-to: <83k2b08dy9.fsf@gnu.org> X-INSM-ip-source: 146.48.81.102 Auth Done X-fingerprint: 4B02 6187 5C03 D6B1 2E31 7666 09DF 2DC9 BE21 6115 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:127171 Archived-At: >> Date: Thu, 15 Dec 2016 17:34:23 +0100 >> From: Francesco Potortì >> >> 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? No :( >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. The echo area always shows the contents of the *Shell Command Output* buffer. When I use the minibuffer, all is well and the minibuffer works as usual. As soon as I finish using it, it again displays the *Shell Command Output* buffer. The cursor never goes there, C-x o does nothing as usual if I have a single buffer int he window. Oh, note that I have two frames open, one running under screen in a virtual terminal and one on X. Only the latter frame exhibits the problem. However, I have just tried to go to the terminal frame, switch to the *Shell Command Output* buffer, and now the problem also happens there! >Do you have some non-nil kill-buffer-hook, and if so, what does that >do? (tramp-flush-file-function browse-url-delete-temp-file preview-kill-buffer-cleanup rmail-mode-kill-summary tramp-delete-temp-file-function uniquify-kill-buffer-function vc-kill-buffer-hook) > What about kill-buffer-query-functions -- any non-nil value for >that? (process-kill-buffer-query-function) >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? No errors... >When you attempt to kill the buffer, do you see any messages added to >*Messages*? Nothing >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 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 :)