From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: compilation-error-regexp-alist syntax problems Date: Thu, 05 Feb 2004 12:40:19 -0700 Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <40229C23.6010205@yahoo.com> References: <401FF0FB.5050008@yahoo.com> <40202108.7060308@yahoo.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1076010589 14661 80.91.224.253 (5 Feb 2004 19:49:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 5 Feb 2004 19:49:49 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Feb 05 20:49:41 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AopVN-0004ct-00 for ; Thu, 05 Feb 2004 20:49:41 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AopS8-00088y-7K for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Feb 2004 14:46:20 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 51 Original-NNTP-Posting-Host: 170.207.51.80 Original-X-Trace: news.uni-berlin.de 1076010016 34138695 D 170.207.51.80 ([82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Original-Xref: shelby.stanford.edu gnu.emacs.help:120724 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:16671 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:16671 Stefan Monnier wrote: >>I don't understand why it's better to evaluate the FORM immediately >>after (provide FEATURE) or how that solves Roy's problem of augmenting a >>list-valued variable defvar'ed in the FILE. The advantage of late > > Assuming the `provide' is where the coding convention says it should be, > then evaluating FORM right after it means that it's evaluated when the file > has already been fully processed, just as Roy needs it. > And since it relies on the feature name rather than ht efile name, it does > not matter how you decided to load the file. But then does it only work for files that provide a feature identical to (the base of) the file name? The implementation of eval-after-load shouldn't depend on users/ programmers adhering to all these various conventions, IMHO. >>I thought it would result in those `defvar's being copied into >>loaddefs.el, which would be dumped into the emacs executable, so they >>could be safely referenced before the "compile" library was actually >>loaded. What am I misunderstanding? > > Look at his add-hook code: it intuitively should work. Yet, even with your > suggestion it won't work. Your suggestion allows setting > compilation-error-regexp-alist directly, but it is of no use when the var > is set from the compilation-mode-hook. Right, but that's because compile-internal overrides any changes to the following variables that compilation-mode-hook might make to them: compilation-parse-errors-function compilation-error-message compilation-error-regexp-alist compilation-enter-directory-regexp-alist compilation-leave-directory-regexp-alist compilation-file-regexp-alist compilation-nomessage-regexp-alist compilation-arguments lazy-lock-defer-on-scrolling default-directory compilation-directory-stack It looks like compilation-process-setup-function is the way to go: | *Function to call to customize the compilation process. | This functions is called immediately before the compilation process is | started. It can be used to set any variables or functions that are used | while processing the output of the compilation process. -- Kevin Rodgers