From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Misc. minor compile.el issues Date: 07 Dec 2002 02:49:09 +0100 Sender: emacs-devel-admin@gnu.org Message-ID: <5x3cpaegyy.fsf@kfs2.cua.dk> References: <5xn0nkasst.fsf@kfs2.cua.dk> <200212061655.gB6GtA208490@rum.cs.yale.edu> <5xisy6j44w.fsf@kfs2.cua.dk> <200212062014.gB6KELU09529@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1039222696 2370 80.91.224.249 (7 Dec 2002 00:58:16 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 7 Dec 2002 00:58:16 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18KTIN-0000c6-00 for ; Sat, 07 Dec 2002 01:58:15 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18KTRF-000579-00 for ; Sat, 07 Dec 2002 02:07:25 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18KTAk-00059P-00; Fri, 06 Dec 2002 19:50:22 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18KT9u-0003mi-00 for emacs-devel@gnu.org; Fri, 06 Dec 2002 19:49:30 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18KT9s-0003ic-00 for emacs-devel@gnu.org; Fri, 06 Dec 2002 19:49:29 -0500 Original-Received: from mail.filanet.dk ([195.215.206.179]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18KT9r-0003ff-00 for emacs-devel@gnu.org; Fri, 06 Dec 2002 19:49:28 -0500 Original-Received: from kfs2.cua.dk.cua.dk (unknown [10.1.82.3]) by mail.filanet.dk (Postfix) with SMTP id 7D0C07C017; Sat, 7 Dec 2002 00:49:25 +0000 (GMT) Original-To: "Stefan Monnier" In-Reply-To: <200212062014.gB6KELU09529@rum.cs.yale.edu> Original-Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:9946 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:9946 "Stefan Monnier" writes: > > > > Related to this, I would like the setup function to be able to > > > > access the buffer and/or window for the compilation process (e.g. > > > > to set buffer-local variables). > > > > > > AFAIK, you can use (current-buffer). No need for `outbuf'. > > > Am I missing something ? > > > > AFAICS, the setup function is (typically) not called with > > current-buffer == outbuf. > > Huh? The only place where it is called seems to be in: > > (with-current-buffer outbuf [...] > (set-window-start outwin (point-min)) > (or (eq outwin (selected-window)) > (set-window-point outwin (point-min))) > (compilation-set-window-height outwin) > (if compilation-process-setup-function > (funcall compilation-process-setup-function)) > > I don't see anything between the with-current-buffer and the call > to compilation-process-setup-function which could change current-buffer. Absolutely true... I was confusing outbuf/current-buffer [which are identical] with outwin/selected-window which are not necessarily the same. But I guess we can live without accessing the outwin... -- Kim F. Storm http://www.cua.dk