all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: emacs-devel@gnu.org
Subject: Re: Updating *vc-dir* marks from *VC-log*
Date: Sat, 20 Nov 2010 23:46:40 -0500	[thread overview]
Message-ID: <yxq4obbthan.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <19688.28312.768696.349949@rgr.rgrjr.com> (Bob Rogers's message of "Sat\, 20 Nov 2010 19\:58\:00 -0500")

Bob Rogers <rogers-emacs@rgrjr.dyndns.org> writes:

>    Perhaps I'm slow, but I only just noticed that it is possible to work
> on multiple VC commits for the same working copy in parallel, just by
> renaming *VC-log* buffers.  This is cool; it perfectly suits my working
> style.  I would like to write it up for the Emacs manual so that others
> can find it.
>
>    But it lacks something.  I often start a commit, then realize that
> I've left out a file or two, or maybe included one that ought to be
> committed separately.  When doing one commit at a time, this is a simple
> matter of returning to vc-dir, updating the set, and doing "C-x v v"
> again.  With multiple pending commits, what is needed is a way to return
> to vc-dir and "swap in" the log buffer fileset.  The patch below adds a
> new log-edit-visit-files-in-vc-dir command to do this.  I have
> tentatively bound it to "C-c @" in log-edit-mode, which I hope is
> sufficiently mnemonic for "mark".

I am not sure what you are trying to do here...
In the *VC log* buffer the vc-parent-buffer buffer-local variable
points to the *vc dir* buffer that was used to create it.
Doesn't this simplify what you are trying to do?



  reply	other threads:[~2010-11-21  4:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21  0:58 Updating *vc-dir* marks from *VC-log* Bob Rogers
2010-11-21  4:46 ` Dan Nicolaescu [this message]
2010-11-21 16:14   ` Bob Rogers
2010-11-21 17:02     ` Dan Nicolaescu
2010-11-21 18:30       ` Bob Rogers
2010-11-23 17:06         ` Dan Nicolaescu
2010-11-21 18:43 ` Stefan Monnier
2010-11-21 20:46   ` Bob Rogers

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=yxq4obbthan.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rogers-emacs@rgrjr.dyndns.org \
    /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.