From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Add M-x occur to the menu-bar Date: 03 Mar 2004 08:27:48 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <3F69E6FF.9050702@yahoo.com> <4n8yjto16h.fsf@collins.bwh.harvard.edu> <4nisixjibl.fsf@collins.bwh.harvard.edu> <20040127230323.GB5407@fencepost> <4n7jzc919v.fsf@collins.bwh.harvard.edu> <4nn085i7nl.fsf@collins.bwh.harvard.edu> <4noese37h0.fsf@collins.bwh.harvard.edu> <4nbrodxwqm.fsf@collins.bwh.harvard.edu> <4n8yjcccvj.fsf@collins.bwh.harvard.edu> <4nwu6sp7ni.fsf@collins.bwh.harvard.edu> Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Az1W2-0001E0-00 for ; Thu, 04 Mar 2004 23:40:30 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Az1W2-0003Dm-00 for ; Thu, 04 Mar 2004 23:40:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1Az1Vk-0003Ay-67 for emacs-devel@quimby.gnus.org; Thu, 04 Mar 2004 17:40:12 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AyWUn-0006Qa-1D for emacs-devel@gnu.org; Wed, 03 Mar 2004 08:33:09 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AyWUE-0006GT-2K for emacs-devel@gnu.org; Wed, 03 Mar 2004 08:33:05 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AyWPg-0005I2-S8 for emacs-devel@gnu.org; Wed, 03 Mar 2004 08:27:52 -0500 Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 5585820528; Wed, 3 Mar 2004 08:27:48 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 48ACE8C8E4; Wed, 3 Mar 2004 08:27:48 -0500 (EST) Original-To: Kevin Rodgers In-Reply-To: <404517D7.7010808@yahoo.com> Original-Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.9, requis 5, BAYES_00 -4.90) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:20241 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20241 > But I would like to give the user some control over that. For instance, > if next-error-last-buffer were a list with the most recently created > buffer at the front (like a stack), the user could go back to his/her > previous next-error task simply by killing the most recent > compile/grep/occur buffer. I'm not sure it's worth the trouble. They can instead select the desired buffer and use next-error in it, which will set next-error-last-buffer. > (Those buffers should remove themselves from > the list when they're killed, so that next-error doesn't have to check > for a dead buffer.) It's probably easier and surely more robust to check for liveness than to reliably remove buffers from the list. Stefan