GNU bug report logs -
#32473
Broken menu entry in manual, section 4.1
Previous Next
Reported by: HiPhish <hiphish <at> posteo.de>
Date: Sun, 19 Aug 2018 13:37:02 UTC
Severity: normal
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32473 in the body.
You can then email your comments to 32473 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#32473
; Package
guix
.
(Sun, 19 Aug 2018 13:37:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
HiPhish <hiphish <at> posteo.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 19 Aug 2018 13:37:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I noticed a broken menu entry in the Info version of the Guix manual: the node
`Defining Packages` (4.1) has an extra space between the last word and the
closing colons:
* package Reference :: The package data type
The standalone Info reader tolerates it, but not the Info.vim reader, which
considers the space to be part of the target node name. Neither the Texinfo
manual (section 4.9) nor the Info manual seem to allow for this extra space,
so it looks like a bug in the manual to me.
PS: I am the author of the Info.vim reader, if that matters.
https://gitlab.com/HiPhish/info.vim
Reply sent
to
ludo <at> gnu.org (Ludovic Courtès)
:
You have taken responsibility.
(Mon, 20 Aug 2018 10:22:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
HiPhish <hiphish <at> posteo.de>
:
bug acknowledged by developer.
(Mon, 20 Aug 2018 10:22:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 32473-done <at> debbugs.gnu.org (full text, mbox):
Hello Hiphish,
HiPhish <hiphish <at> posteo.de> skribis:
> I noticed a broken menu entry in the Info version of the Guix manual: the node
> `Defining Packages` (4.1) has an extra space between the last word and the
> closing colons:
>
> * package Reference :: The package data type
Oops, I’ve fixed this now in guix.texi (commit
fa4ebd2f08d0acc25feca827f7e43e8774843a10).
> The standalone Info reader tolerates it, but not the Info.vim reader, which
> considers the space to be part of the target node name. Neither the Texinfo
> manual (section 4.9) nor the Info manual seem to allow for this extra space,
> so it looks like a bug in the manual to me.
Would it make sense for Info.vim to be bug-compatible?
Thanks for your report,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#32473
; Package
guix
.
(Tue, 21 Aug 2018 11:06:01 GMT)
Full text and
rfc822 format available.
Message #13 received at submit <at> debbugs.gnu.org (full text, mbox):
On Montag, 20. August 2018 12:21:07 CEST you wrote:
> > The standalone Info reader tolerates it, but not the Info.vim reader,
> > which
> > considers the space to be part of the target node name. Neither the
> > Texinfo
> > manual (section 4.9) nor the Info manual seem to allow for this extra
> > space, so it looks like a bug in the manual to me.
>
> Would it make sense for Info.vim to be bug-compatible?
I considered that, but I don't think it's a good idea: it's better to fix a
bug (when feasible of course) than to sweep it under the rug with some hack.
If the bug is fixed, it's fixed for everyone, if I make Info.vim bug-
compatible I make my reader harder to maintain and that bug still persists and
will eventually bite someone when they want to implement their own Info
reader.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#32473
; Package
guix
.
(Tue, 21 Aug 2018 21:41:01 GMT)
Full text and
rfc822 format available.
Message #16 received at submit <at> debbugs.gnu.org (full text, mbox):
HiPhish <hiphish <at> posteo.de> skribis:
> On Montag, 20. August 2018 12:21:07 CEST you wrote:
>> > The standalone Info reader tolerates it, but not the Info.vim reader,
>> > which
>> > considers the space to be part of the target node name. Neither the
>> > Texinfo
>> > manual (section 4.9) nor the Info manual seem to allow for this extra
>> > space, so it looks like a bug in the manual to me.
>>
>> Would it make sense for Info.vim to be bug-compatible?
>
> I considered that, but I don't think it's a good idea: it's better to fix a
> bug (when feasible of course) than to sweep it under the rug with some hack.
> If the bug is fixed, it's fixed for everyone, if I make Info.vim bug-
> compatible I make my reader harder to maintain and that bug still persists and
> will eventually bite someone when they want to implement their own Info
> reader.
Yes, that makes a lot of sense to me. Thanks for your feedback!
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 19 Sep 2018 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 192 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.