From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.devel Subject: Re: "Recent" changes to compilation-mode? Date: Mon, 23 May 2005 09:25:11 -0400 Message-ID: References: <17040.64813.804833.286809@farnswood.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1116855035 22745 80.91.229.2 (23 May 2005 13:30:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 May 2005 13:30:35 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 23 15:30:32 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DaCyW-0004Mw-CZ for ged-emacs-devel@m.gmane.org; Mon, 23 May 2005 15:28:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DaD1y-0004XB-RO for ged-emacs-devel@m.gmane.org; Mon, 23 May 2005 09:31:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DaD0q-0004Ds-OQ for emacs-devel@gnu.org; Mon, 23 May 2005 09:30:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DaD0p-0004DJ-Ja for emacs-devel@gnu.org; Mon, 23 May 2005 09:30:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DaD0p-0004CX-FG for emacs-devel@gnu.org; Mon, 23 May 2005 09:30:31 -0400 Original-Received: from [207.172.4.63] (helo=smtp04.mrf.mail.rcn.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DaD66-0001ar-SB for emacs-devel@gnu.org; Mon, 23 May 2005 09:35:59 -0400 Original-Received: from 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com (HELO I9300.boost-consulting.com) (146.115.127.135) by smtp04.mrf.mail.rcn.net with ESMTP; 23 May 2005 09:25:09 -0400 X-IronPort-AV: i="3.93,128,1115006400"; d="scan'208"; a="38150765:sNHT21568488" Original-To: Nick Roberts In-Reply-To: <17040.64813.804833.286809@farnswood.snap.net.nz> (Nick Roberts's message of "Mon, 23 May 2005 09:44:13 +1200") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (windows-nt) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:37513 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37513 Nick Roberts writes: > > Second, next-error used to cause the error in question to scroll to > > the top of the *compilation* buffer's window, which made it very easy > > to see what was going on. Now emacs just moves that buffer's point > > without scrolling. Since the active point ends up in the source > > file's buffer where the error is, all I see change in the > > *compilation* buffer is that an unfilled rectangle with super-thin > > borders moves. It's extremely hard to see; if the window isn't going > > to scroll, IMO something else needs to be done (e.g. with > > highlighting) to emphasize the error in question. > > > When there is a fringe present, the default was changed to not scroll > because the arrow points to the current error and errors immediately > above the current one remain visible. > > When there is no fringe, the current error scrolls to the top of the > *compilation* buffer's window. > > So you should either see an arrow or scrolling. If you don't, you need > to give your configuration. M-x report-emacs-bug, also on the menu bar > plus the value of fringe-mode and/or window-fringes is a good start. Yeah, there's a tiny arrow there. The problem is that the diagnostics typically span several lines and are often quite dense, and the arrow isn't quite enough to help me distinguish the boundaries of the diagnostic being indicated by the arrow. Would it be possible to add some kind of highlighting to the current error, similar to what I get when hovering the mouse over it? > P.S To always scroll to the top: (setq compilation-context-lines 0) Ah, that will be a big help, thanks. Not quite as good as highlighting, but not bad. -- Dave Abrahams Boost Consulting www.boost-consulting.com