[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called fro
From: |
Eli Zaretskii |
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: |
Sun, 11 Jun 2023 08:06:21 +0300 |
> Date: Sat, 10 Jun 2023 23:18:01 +0200
> Cc: manuel@ledu-giraud.fr, 63949@debbugs.gnu.org
> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
>
> On 2023-06-10 19:23, Eli Zaretskii wrote:
>
> > If the backend is a VCS that records changes per-file, what you want
> > will happen automatically, since "C-x v l" and other operations must
> > in general refer to a file with those VCSes. For backends that
> > record changes per-repository, why does it make sense that typing
> > "C-x v l" from a buffer that already shows a log should produce the
> > same log again?
>
> To get it updated, for example because I perform some operation outside
> of Emacs. One of these habits ...
If there's more than one natural meaning of a command, the usual way
we solve the dilemma is by using a prefix argument.
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, (continued)
- 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, 2023/06/08
- 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, 2023/06/08
- 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, 2023/06/08
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/09
- 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, 2023/06/09
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/10
- 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, 2023/06/10
- 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, 2023/06/10
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/10
- 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, 2023/06/10
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs,
Eli Zaretskii <=
- 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, 2023/06/16
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/16
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/17
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/18
- 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, 2023/06/18
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/18
- Message not available
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/19
- 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, 2023/06/21
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/21
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/21