From: Sven Joachim <svenjoac@gmx.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 21955@debbugs.gnu.org
Subject: bug#21955: 25.0.50; vc-next-action fails from *vc-change-log* buffer
Date: Wed, 18 Nov 2015 20:42:57 +0100 [thread overview]
Message-ID: <87y4dvgkla.fsf@turtle.gmx.de> (raw)
In-Reply-To: <564CC911.7090702@yandex.ru> (Dmitry Gutov's message of "Wed, 18 Nov 2015 20:53:05 +0200")
On 2015-11-18 20:53 +0200, Dmitry Gutov wrote:
> On 11/18/2015 08:47 PM, Sven Joachim wrote:
>> Visit some file in a git repository, make a change and save it. Press
>> C-x v l do view the file's version history. Press C-x v v to commit
>> your changes. Result is an error:
>
> I'm sure it should work that way. `C-x v v' committing the current
> file is fine, but you've switched to a different buffer.
It used to work in Emacs 24, and I have come to rely on that behavior.
Apparently the fix for bug #19084 changed it, vc-deduce-fileset in the
*vc-change-log* buffer no longer returns the file whose history is
displayed, but rather the directory it is in.
> Do we promise
> the behavior you want somewhere in the documentation?
Not explicitly, but I find it a bit surprising (and annoying) that the
command to list the changelog of a fileset does not preserve that same
fileset in the log buffer.
Certainly the behavior of C-x v L is more correct now, but the one of
C-x v l has regressed.
>> vc-next-action: Wrong type argument: listp, "/usr/local/src/emacs/"
>
> I can make it fail with a more comprehensible error message.
That's the least I would expect.
Cheers,
Sven
next prev parent reply other threads:[~2015-11-18 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:47 bug#21955: 25.0.50; vc-next-action fails from *vc-change-log* buffer Sven Joachim
2015-11-18 18:53 ` Dmitry Gutov
2015-11-18 19:42 ` Sven Joachim [this message]
2015-11-19 1:40 ` Dmitry Gutov
2015-11-19 18:24 ` Sven Joachim
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=87y4dvgkla.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=21955@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.