From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Cc: 63949@debbugs.gnu.org, manuel@ledu-giraud.fr
Subject: bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs
Date: Fri, 09 Jun 2023 09:09:36 +0300 [thread overview]
Message-ID: <83y1kt180v.fsf@gnu.org> (raw)
In-Reply-To: <7bc0c78e-e4b5-0edc-0e9f-2f8fbafc352f@vodafonemail.de> (bug-gnu-emacs@gnu.org)
> Cc: 63949@debbugs.gnu.org
> Date: Fri, 9 Jun 2023 00:10:57 +0200
> From: Jens Schmidt via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Caused by commit d494833d47968fcd97ba549654a259d6fb6c2eee.
Which means this was a regression in Emacs 28, and we should try to
fix it in Emacs 29.
> There is another subtle change to (most likely) that, which seems to
> affect all backends: When calling `vc-print-log' from
> *vc-change-buffer*, it now modifies the VC parent buffer to itself,
> which is of course incorrect.
What do you mean by "modifies the VC parent buffer to itself"? Do you
mean that vc-print-log makes the *vc-change-buffer* be the VC parent
buffer? If so, why is this incorrect?
next prev parent reply other threads:[~2023-06-09 6:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 21:04 bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 13:12 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 20:21 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 21:33 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 22:10 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-09 6:09 ` Eli Zaretskii [this message]
2023-06-09 20:27 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 6:01 ` Eli Zaretskii
2023-06-10 15:44 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 15:55 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 17:23 ` Eli Zaretskii
2023-06-10 21:18 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 5:06 ` Eli Zaretskii
2023-06-16 19:33 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 3:15 ` Dmitry Gutov
2023-06-18 2:42 ` Dmitry Gutov
2023-06-18 5:35 ` Eli Zaretskii
2023-06-18 9:11 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 12:00 ` Dmitry Gutov
[not found] ` <e695eaa4-2f39-1b20-1cd4-fe7fdaeb3d61@vodafonemail.de>
2023-06-20 2:41 ` Dmitry Gutov
2023-06-21 13:03 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 14:37 ` Dmitry Gutov
2023-06-21 15:30 ` Eli Zaretskii
2023-06-24 3:08 ` Dmitry Gutov
2023-06-26 19:54 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-29 21:37 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 5:57 ` Eli Zaretskii
2023-07-17 19:53 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 0:55 ` Dmitry Gutov
2023-07-18 11:08 ` Eli Zaretskii
2023-06-08 22:44 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-09 6:41 ` Eli Zaretskii
2023-06-09 18:44 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 23:09 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83y1kt180v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63949@debbugs.gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=manuel@ledu-giraud.fr \
/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.