From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Introducing 'unrecognized and 'ignored Date: Mon, 21 Jan 2008 10:56:23 -0500 Message-ID: References: <17EA38DF-BCC1-4565-8510-5DD10DD667E3@mac.com> <20071229114551.GD9794@thyrsus.com> <20080102021907.GA15494@thyrsus.com> <200801020445.m024jWU2008538@oogie-boogie.ics.uci.edu> <200801031805.m03I5SBf022748@oogie-boogie.ics.uci.edu> <200801050901.m0591mQj011970@oogie-boogie.ics.uci.edu> <20080105143415.GG30869@thyrsus.com> <200801061037.m06AbIRD004966@oogie-boogie.ics.uci.edu> <200801182346.m0INkiEg022130@sallyv1.ics.uci.edu> <200801191705.m0JH5WOU026943@sallyv1.ics.uci.edu> <87sl0tbn1m.fsf@ambire.localdomain> <87myr0qlyp.fsf@ambire.localdomain> <200801211530.m0LFUxpZ004358@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1200931140 24972 80.91.229.12 (21 Jan 2008 15:59:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Jan 2008 15:59:00 +0000 (UTC) Cc: Thien-Thi Nguyen , emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 21 16:59:18 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JGz3L-0007CC-Fo for ged-emacs-devel@m.gmane.org; Mon, 21 Jan 2008 16:59:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGz2w-0004JY-3g for ged-emacs-devel@m.gmane.org; Mon, 21 Jan 2008 10:58:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JGz0c-0002iS-2o for emacs-devel@gnu.org; Mon, 21 Jan 2008 10:56:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JGz0b-0002hq-7M for emacs-devel@gnu.org; Mon, 21 Jan 2008 10:56:25 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JGz0b-0002hf-3g for emacs-devel@gnu.org; Mon, 21 Jan 2008 10:56:25 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JGz0a-0008O6-RP for emacs-devel@gnu.org; Mon, 21 Jan 2008 10:56:25 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAGxPlEfO+IHadGdsb2JhbACQGgEwmkx+ X-IronPort-AV: E=Sophos;i="4.25,227,1199682000"; d="scan'208";a="12997340" Original-Received: from smtp.pppoe.ca ([65.39.196.238]) by ironport2-out.pppoe.ca with ESMTP; 21 Jan 2008 10:56:23 -0500 Original-Received: from pastel.home ([206.248.129.218]) by smtp.pppoe.ca (Internet Mail Server v1.0) with ESMTP id BQZ95323; Mon, 21 Jan 2008 10:56:23 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 6D7317F61; Mon, 21 Jan 2008 10:56:23 -0500 (EST) In-Reply-To: <200801211530.m0LFUxpZ004358@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Mon, 21 Jan 2008 07:30:53 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:87218 Archived-At: >> > This can't be right: we have no idea what buffer we're in at this point. >> >> > you're right. i have just installed a `with-current-buffer' wrapper. >> >> >> + (setq mode-line-process " (background)") >> >> > The problem with this is that it's not necessarily clear that we're >> > changing mode-line-process in the right buffer either, here. >> >> > PROC is taken from (current-buffer). is that not reliable? >> >> It's reliable in that we know which buffer it is, but that doesn't mean >> it's the right buffer. Isn't it often a hidden buffer like *vc* rather >> than the vc-status buffer itself? > Yep, this seems to work for things like log, diff, annotate, but for > vc-status it does not, because as you say, the status command does not > run in vc-status buffer, but in a hidden temporary buffer. > It seems that a different mechanism is needed for that case. Yes, I guess the change is fine, and just needs to be supplemented with some special code for vc-status. Stefan