unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: 9409@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	14531@debbugs.gnu.org
Subject: bug#14531: 24.3.50; `log-view-file-prev' doesn't move to the beginning of the log buffer
Date: Thu, 05 May 2022 14:28:00 +0200	[thread overview]
Message-ID: <87mtfwqi3z.fsf@gnus.org> (raw)
In-Reply-To: <87pn6aqfvs.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 25 Sep 2020 13:01:43 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> In (info "(emacs) VC Change Log"):
>>   `P'
>>      Move to the log of the previous file, if showing logs for a
>>      multi-file VC fileset.  Otherwise, just move to the beginning of
>>      the log.  A numeric prefix argument is a repeat count.
>>
>> I tried visiting a random Emacs Lisp file (calc.el) in the bzr repo, and
>> then execute `vc-print-log'.  It isn't a multi-file fileset, but
>> pressing `P' does not move to the beginning of the log buffer.  Instead,
>> an error message "No previous file" occurs.
>
> I'm not sure what that command is meant to do, even after reading the
> documentation and reading the code (and even reading the code doesn't
> help that much, because these are easy-mmode-define-navigation
> incantation).
>
> It searches for the prev instance of:
>
> log-view-file-re
> "^\\(?:Working file: \\(?1:.+\\)\\|\\(?:SCCS/s\\.\\|Changes to
> \\)\\(?1:.+\\):\\)
> "
>
> in the *vc-change-log* buffer?  But ... there's nothing like that in a
> git buffer?
>
> So `P'/`N' always fails for me.  Is this just code that has bitrotted,
> or is the use case just not...  explained well?

Perhaps these commands are CVS/RCS/SCCS-specific, and shouldn't be
enabled in general?  Because they're pretty confusing as is, and should
(at the very least) explain better what they're attempting to do.

I've added Stefan and Dmitry to the CCs; perhaps they have some insights
here.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-05 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02  2:53 bug#14531: 24.3.50; `log-view-file-prev' doesn't move to the beginning of the log buffer Xue Fuqiao
2013-06-04  1:12 ` Glenn Morris
2020-09-25 11:01 ` bug#9409: " Lars Ingebrigtsen
2022-05-05 12:28   ` Lars Ingebrigtsen [this message]
2022-05-05 19:58     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-06 11:45       ` Lars Ingebrigtsen

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=87mtfwqi3z.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=14531@debbugs.gnu.org \
    --cc=9409@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=monnier@iro.umontreal.ca \
    --cc=xfq.free@gmail.com \
    /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).