From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: "Recent" changes to compilation-mode? Date: Mon, 23 May 2005 09:44:13 +1200 Message-ID: <17040.64813.804833.286809@farnswood.snap.net.nz> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1116798281 14774 80.91.229.2 (22 May 2005 21:44:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 22 May 2005 21:44:41 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 22 23:44:38 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DZyF6-00026s-2d for ged-emacs-devel@m.gmane.org; Sun, 22 May 2005 23:44:16 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DZyIQ-0001IM-AH for ged-emacs-devel@m.gmane.org; Sun, 22 May 2005 17:47:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DZyGr-0000NI-Kt for emacs-devel@gnu.org; Sun, 22 May 2005 17:46:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DZyGq-0000Lj-0v for emacs-devel@gnu.org; Sun, 22 May 2005 17:46:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DZyGp-0000LB-JY for emacs-devel@gnu.org; Sun, 22 May 2005 17:46:03 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DZyNf-0000PX-1N for emacs-devel@gnu.org; Sun, 22 May 2005 17:53:07 -0400 Original-Received: from farnswood.snap.net.nz (p115-tnt1.snap.net.nz [202.124.110.115]) by viper.snap.net.nz (Postfix) with ESMTP id D84C4535502; Mon, 23 May 2005 09:43:42 +1200 (NZST) Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 9B28262A99; Sun, 22 May 2005 22:44:14 +0100 (BST) Original-To: David Abrahams In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.55 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:37479 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37479 > 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. Nick P.S To always scroll to the top: (setq compilation-context-lines 0)