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: "Recent" changes to compilation-mode? Date: Sun, 22 May 2005 07:37:06 -0400 Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1116761854 26747 80.91.229.2 (22 May 2005 11:37:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 22 May 2005 11:37:34 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 22 13:37:32 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DZoli-0003n9-T4 for ged-emacs-devel@m.gmane.org; Sun, 22 May 2005 13:37:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DZoox-0005rZ-NV for ged-emacs-devel@m.gmane.org; Sun, 22 May 2005 07:40:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DZooC-0005gW-JZ for emacs-devel@gnu.org; Sun, 22 May 2005 07:39:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DZoo4-0005cx-UY for emacs-devel@gnu.org; Sun, 22 May 2005 07:39:45 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DZoo4-0005au-ED for emacs-devel@gnu.org; Sun, 22 May 2005 07:39:44 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DZov0-0007Fs-Mu for emacs-devel@gnu.org; Sun, 22 May 2005 07:46:54 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DZokX-0003iv-Ba for emacs-devel@gnu.org; Sun, 22 May 2005 13:36:05 +0200 Original-Received: from 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com ([146.115.127.135]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 May 2005 13:36:05 +0200 Original-Received: from dave by 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 May 2005 13:36:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 44 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 146-115-127-135.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (windows-nt) Cancel-Lock: sha1:9jBJQp3fXkHwJrUb9NqZsSkaAUM= 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:37466 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37466 Sometime in the past year or so compilation-mode started acting very strangely for me with a CVS-built emacs. First, if I use next-error while compilation is still going on, I will often, after a moment or two, see the point jump unpredictably in the file it takes me to. 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. Finally, many of my carefully-constructed error regexps seem no longer to be recognized. I had been doing: (require 'compile) (setq compilation-error-regexp-alist (append '(...regexps...) compilation-error-regexp-alist)) (if (fboundp 'compilation-file-regexp-alist) ; in case of XEmacs, ; which doesn't support ; 'compilation-file-regexp-alist (setq compilation-file-regexp-alist (append '(... regexps ...) compilation-file-regexp-alist))) I note that now there appears to be a two-layer scheme with compilation-error-regexp-alist-alist that renders my old settings invalid. I can adjust what I'm doing, but discovering what to do was a struggle. Is there a way to provide a better transition experience for people who upgrade? -- Dave Abrahams Boost Consulting www.boost-consulting.com