From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: emacs-devel@gnu.org
Subject: Re: The VC to-do list
Date: Fri, 02 May 2008 22:50:17 -0700 [thread overview]
Message-ID: <200805030550.m435oI0Q014899@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <20080502211447.207E09F051D@snark.thyrsus.com> (Eric S. Raymond's message of "Fri, 2 May 2008 17:14:47 -0400 (EDT)")
"Eric S. Raymond" <esr@snark.thyrsus.com> 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.
> (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.
> (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.
next prev parent reply other threads:[~2008-05-03 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 21:14 The VC to-do list Eric S. Raymond
2008-05-03 2:59 ` Stefan Monnier
2008-05-03 6:03 ` Eric S. Raymond
2008-05-03 19:19 ` Stefan Monnier
2008-05-03 23:03 ` Eric S. Raymond
2008-05-03 5:50 ` Dan Nicolaescu [this message]
2008-05-03 6:10 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805030550.m435oI0Q014899@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).