GNU bug report logs - #10864
kill output buffer on "no match"

Previous Next

Package: emacs;

Reported by: sds <at> gnu.org

Date: Tue, 21 Feb 2012 21:32:01 UTC

Severity: wishlist

Tags: wontfix

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 10864 in the body.
You can then email your comments to 10864 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#10864; Package emacs. (Tue, 21 Feb 2012 21:32:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to sds <at> gnu.org:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Tue, 21 Feb 2012 21:32:01 GMT) Full text and rfc822 format available.

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

From: Sam Steingold <sds <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org
Subject: kill output buffer on "no match"
Date: Tue, 21 Feb 2012 16:27:55 -0500
In GNU Emacs 24.0.93.3 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2012-02-20 on t520sds
Windowing system distributor `The X.Org Foundation', version 11.0.11004000
Configured using:
 `configure '--with-wide-int''

it would be nice if commands like grep, rgrep, find-dired et al killed
their output buffers when the search returned no matches, at least as an
option.


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://www.memritv.org http://palestinefacts.org
http://americancensorship.org http://ffii.org http://mideasttruth.com
(lisp programmers do it better)




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#10864; Package emacs. (Sat, 17 Aug 2019 23:52:01 GMT) Full text and rfc822 format available.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 10864 <at> debbugs.gnu.org
Cc: sds <at> gnu.org
Subject: Re: bug#10864: kill output buffer on "no match"
Date: Sat, 17 Aug 2019 16:50:56 -0700
Sam Steingold <sds <at> gnu.org> writes:

> it would be nice if commands like grep, rgrep, find-dired et al killed
> their output buffers when the search returned no matches, at least as an
> option.

(I'm going through old bug reports that unfortunately have gotten no
responses yet.)

Hm...  I think that sounds like somewhat surprising behaviour, and my
feeling is that not many people would want this, so I'm closing this as
a "wontfix".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




Added tag(s) wontfix. Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sat, 17 Aug 2019 23:52:02 GMT) Full text and rfc822 format available.

bug closed, send any further explanations to 10864 <at> debbugs.gnu.org and sds <at> gnu.org Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sat, 17 Aug 2019 23:52:02 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 15 Sep 2019 11:24:07 GMT) Full text and rfc822 format available.

This bug report was last modified 4 years and 222 days ago.

Previous Next


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