From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: next-error-last-buffer Date: Wed, 12 May 2004 15:42:12 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <871xluig40.fsf@mail.jurta.org> <873c6983t9.fsf@mail.jurta.org> <8765b3vm0r.fsf@mail.jurta.org> <4nn04fgeli.fsf@lifelogs.com> <87hdumto1j.fsf@mail.jurta.org> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1084392307 9838 80.91.224.253 (12 May 2004 20:05:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 12 May 2004 20:05:07 +0000 (UTC) Cc: tzz@lifelogs.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed May 12 22:04:54 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNzyH-00011E-00 for ; Wed, 12 May 2004 22:04:53 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNzyH-0006Ia-00 for ; Wed, 12 May 2004 22:04:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNzxd-0003tT-36 for emacs-devel@quimby.gnus.org; Wed, 12 May 2004 16:04:13 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNzxC-0003lW-EI for emacs-devel@gnu.org; Wed, 12 May 2004 16:03:46 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNzwZ-0003c9-9h for emacs-devel@gnu.org; Wed, 12 May 2004 16:03:43 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNzcL-0006cX-3t for emacs-devel@gnu.org; Wed, 12 May 2004 15:42:13 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BNzcK-0007r5-QR; Wed, 12 May 2004 15:42:12 -0400 Original-To: Juri Linkov In-reply-to: <87hdumto1j.fsf@mail.jurta.org> (message from Juri Linkov on Wed, 12 May 2004 02:46:48 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 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:23275 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23275 1. Add an option to allow the user to select among predefined behaviors. Though, this will not help the user if he will not find a desired option in the predefined set. I don't want to offer the user a choice of several behaviors that are all unsatisfactory in various ways. This way lies lots of complexity without really satisfying anyone. What we should do, when we see how, is make the default behavior better. 2. Add a new user variable `next-error-find-buffer-function' and try to call it (i.e. to call it if it's fbound and return its value, but if it returns `nil', try other rules) in `next-error-find-buffer' at the top precedence level before all other rules. Is this really an improvement? It is not that hard for users who want different behavior to edit the code. I thought again about why the current behavior is too confusing and I think I found the reason: the most confusing is the fact that the compilation buffer is visible in the window adjacent to the source file window where the point is located, but typing C-x ` uses the last but not visible compilation buffer. Perhaps next-error should always choose a compilation or occur buffer that is visible in a window, rather than one that isn't. And it should prefer one that is visible in the current frame to one that is visible in another frame. This might help us get a better default behavior.