GNU bug report logs - #25406
24.5; doc string of `Info-history'

Previous Next

Full log

Message #13 received at 25406 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25406 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#25406: 24.5; doc string of `Info-history'
Date: Fri, 5 Jul 2019 14:17:39 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Mon, 9 Jan 2017 08:39:13 -0800 (PST)
>> From: Drew Adams <drew.adams <at> oracle.com>
>>
>> The doc string of `Info-find-emacs-command-nodes' refers you to variable
>> `Info-history' for the format of the locations.
>>
>> But the doc for `Info-history' says nothing about FILENAME, NODENAME,
>> and BUFFERPOS.
>>
>> Instead, those are described in `Info-find-emacs-command-nodes'.
>
> Yes, and that is consistent with the text of the doc string.
>
>> Something is backwards here, and/or missing.  Why refer to "the format
>> used in the variable `Info-history' if consulting that variable tells
>> you less about the format that what you are told before sending you
>> there?
>
> While the reference to Info-history might be redundant to some degree,
> I see nothing wrong with it -- or the rest of the text.
>
>>  ", where BUFFERPOS is the line number
>>  of the first element of the returned list (which is treated specially
>>  in `Info-goto-emacs-command-node'), and 0 for the other elements of
>>  the list."
>>
>> But why the parenthetical remark, and what it really means, I have
>> no idea.
>
> It is a hint for why BUFFERPOS is non-zero only in that first element.
> That hint is only important to someone who wants to understand how the
> code works.

It seems to me that the conclusion here is to do nothing.  Can we close
this bug report or am I missing something?

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.