From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric S. Raymond" Newsgroups: gmane.emacs.devel Subject: Re: The VC to-do list Date: Sat, 3 May 2008 02:10:20 -0400 Organization: Eric Conspiracy Secret Labs Message-ID: <20080503061020.GC4217@thyrsus.com> References: <20080502211447.207E09F051D@snark.thyrsus.com> <200805030550.m435oI0Q014899@sallyv1.ics.uci.edu> Reply-To: esr@thyrsus.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1209795013 25956 80.91.229.12 (3 May 2008 06:10:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 May 2008 06:10:13 +0000 (UTC) Cc: "Eric S. Raymond" , emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 03 08:10:48 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 1JsAxI-0005ZY-TT for ged-emacs-devel@m.gmane.org; Sat, 03 May 2008 08:10:45 +0200 Original-Received: from localhost ([127.0.0.1]:37667 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsAwb-0004YI-CM for ged-emacs-devel@m.gmane.org; Sat, 03 May 2008 02:10:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JsAwW-0004WJ-Ce for emacs-devel@gnu.org; Sat, 03 May 2008 02:09:56 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JsAwU-0004Vb-Cz for emacs-devel@gnu.org; Sat, 03 May 2008 02:09:54 -0400 Original-Received: from [199.232.76.173] (port=59857 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsAwU-0004VX-4H for emacs-devel@gnu.org; Sat, 03 May 2008 02:09:54 -0400 Original-Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=snark.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JsAwT-0005KZ-QJ for emacs-devel@gnu.org; Sat, 03 May 2008 02:09:53 -0400 Original-Received: by snark.thyrsus.com (Postfix, from userid 1000) id 824C29F051D; Sat, 3 May 2008 02:10:20 -0400 (EDT) Content-Disposition: inline In-Reply-To: <200805030550.m435oI0Q014899@sallyv1.ics.uci.edu> X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:96365 Archived-At: Dan Nicolaescu : > "Eric S. Raymond" writes: > >> (1) ;; - vc-dir-kill-dir-status-process should not be specific to dir-status, >> ;; it should work for other async commands as well (pull/push/...). >> >> Agreed. Even the async diff code is in this category >> >> Dan, the near term VC-specific fix for this one should probably be >> yours, if you can find time to do it; I don't understand the ewoc >> interface well enough yet, and there are other things I should do to >> VC that are more urgent than learning ewoc. Like item (2). > > This is actually Stefan's addition. It shouldn't be too hard to fix: > all the asynchronous commands need a buffer to run in, just find a way > to keep track of that buffer and kill it+the associated process when > necessary. Agreed. The dispatcher layer I'm thinking about splitting out would need this as a generic facility anyway. > > (11) ;; - add a mechanism for ignoring files. > > > > I'm not clear why. Under what circumstances do we need this when > > the VCS doesn't do it for us? > > This is about adding a way to tell the VCS to ignore certain files. Right; am rewording the to-do appropriately. >> (23) ;; - vc-dir listing needs a footer generated when it's done to make it >> ;; obvious that it has finished. >> >> This is totally a ewoc interface issue. Yours, Dan, I think. > > I'm not convinced it's useful, the mode-line displays [Waiting...] when > something is going on. Really? I didn't notice that...which tells its own story. -- Eric S. Raymond