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: new compile command doesn't coalesce errors on the same line Date: Sat, 20 Mar 2004 23:59:41 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040317215208.5b0cb3e2.occitan@esperanto.org> <20040317224726.GC12561@fencepost> <20040320074137.2ea2c886.occitan@esperanto.org> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1079845816 19761 80.91.224.253 (21 Mar 2004 05:10:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 21 Mar 2004 05:10:16 +0000 (UTC) Cc: miles@lsi.nec.co.jp, emacs-devel@gnu.org, monnier@iro.umontreal.ca, miles@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Mar 21 06:10:12 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 1B4vDw-0001h0-00 for ; Sun, 21 Mar 2004 06:10:12 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B4vDs-0005Y6-01 for ; Sun, 21 Mar 2004 06:10:12 +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 1B4vCt-0003NM-Mf for emacs-devel@quimby.gnus.org; Sun, 21 Mar 2004 00:09:07 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B4v8K-0001ZX-91 for emacs-devel@gnu.org; Sun, 21 Mar 2004 00:04:24 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B4v7t-0001Qc-5n for emacs-devel@gnu.org; Sun, 21 Mar 2004 00:04:19 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B4v7s-0001QV-UM for emacs-devel@gnu.org; Sun, 21 Mar 2004 00:03:56 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.24) id 1B4v3l-0008Fv-6a; Sat, 20 Mar 2004 23:59:41 -0500 Original-To: Daniel Pfeiffer In-reply-to: <20040320074137.2ea2c886.occitan@esperanto.org> (dapfy@t-online.de) 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:20667 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20667 > Meanwhile, to the extent I can figure it out, I think this is indeed > something else. Let's just change the code so as to treat > contiguous errors as one. How contiguous do they have to be? I'd suggest that if one error and the next error point to the same location then they are contiguous. What would we gain? Why would I want to go to the same spot again if it is mentioned 3 lines down, but not when it is mentioned on the next line? The point is to do the convenient thing in a simple common case of multiple errors from a single line. What happens in the strange cases is less important because they are rare. So you may as well handle them in whatever way seems most correct.