all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: tromey@redhat.com
Cc: emacs-devel@gnu.org
Subject: Re: some vc-status updates
Date: Tue, 08 Jan 2008 23:28:45 -0800	[thread overview]
Message-ID: <200801090728.m097Son4004816@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <m3bq7vpyxl.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue,  08 Jan 2008 18:31:18 -0700")

Tom Tromey <tromey@redhat.com> writes:

  > This adds a bunch of functionality to vc-status.

Thanks, I checked this in.

  > * vc-diff does not work unless you have a file marked.  Maybe
  >   vc-status-marked-files should return the current directory in this
  >   case?

Doing the same thing as vc-dired: diff the current files seems like the
most conservative version. I did this.

  > Mostly this was an experiment, to see how easy it would be to turn
  > vc-status into a pcvs replacement.  It doesn't look super hard, I
  > guess, though there is still a good amount to do.  In particular:
  > 
  > * Asynchronous operation

The backend status call needs to be done with vc-exec-after. 

  > * Updates.  Can you do a full-directory update in VC?  

Probably not. But update needs a bit of work anyway: it does not work
for VCSes that only do whole repository updates at a time (hg, git).

  > * A new backend method for "ignore".
  > * Saving buffers should probably update the vc-status buffer.

PCL-CVS does that. Can that code be "stolen"?

  reply	other threads:[~2008-01-09  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  1:31 some vc-status updates Tom Tromey
2008-01-09  7:28 ` Dan Nicolaescu [this message]
2008-01-10  2:00   ` Tom Tromey
2008-01-10  4:01     ` Stefan Monnier
2008-01-10  8:04     ` Dan Nicolaescu
2008-01-18 23:22 ` Dan Nicolaescu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801090728.m097Son4004816@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=tromey@redhat.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.