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: Sun, 21 Nov 2010 12:02:19 -0500 [thread overview]
Message-ID: <yxqvd3qfw4k.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <19689.17740.876119.178798@rgr.rgrjr.com> (Bob Rogers's message of "Sun\, 21 Nov 2010 11\:14\:04 -0500")
Bob Rogers <rogers-emacs@rgrjr.dyndns.org> writes:
> From: Dan Nicolaescu <dann@gnu.org>
> Date: Sat, 20 Nov 2010 23:46:40 -0500
>
> Bob Rogers <rogers-emacs@rgrjr.dyndns.org> writes:
>
> > . . . 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?
>
> Hmm. It could conceivably make vc-dir-find-buffer-for-file unnecessary.
> (I had written that for another hack where vc-parent-buffer may not be
> defined, or may not point to a vc-dir buffer, and just used it
> unthinkingly here.)
>
> On the other hand, one would have to assume that users only want to
> adjust the filesets of commits started from vc-dir buffers.
> vc-dir-find-buffer-for-file would still be useful if the user originally
> typed "C-x v v" in a file buffer, and then had second thoughts.
It's still unclear what you are trying to do, could you please
describe in detail the use-case you have in mind?
>
> But, at the very least, I ought to check vc-parent-buffer first,
> since that would always DTRT if the file appears in multiple vc-dir
> buffers. Thanks for making that apparent.
>
> BTW, this is a subproject that came up while trying to make Emacs
> smarter about changing marked files in vc-dir during the commit (see
> bug#7350).
That's quite easy (I have it in my local copy).
`log-edit-files' gives you a list of files that *VC log* would check in.
`vc-deduce-fileset' in `vc-parent-buffer' gives you the currently selected files in *vc dir*
next prev parent reply other threads:[~2010-11-21 17:02 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
2010-11-21 16:14 ` Bob Rogers
2010-11-21 17:02 ` Dan Nicolaescu [this message]
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
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=yxqvd3qfw4k.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 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).