* bug#32473: Broken menu entry in manual, section 4.1
@ 2018-08-19 12:39 HiPhish
2018-08-20 10:21 ` Ludovic Courtès
0 siblings, 1 reply; 4+ messages in thread
From: HiPhish @ 2018-08-19 12:39 UTC (permalink / raw)
To: 32473
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#32473: Broken menu entry in manual, section 4.1
2018-08-19 12:39 bug#32473: Broken menu entry in manual, section 4.1 HiPhish
@ 2018-08-20 10:21 ` Ludovic Courtès
2018-08-21 10:56 ` HiPhish
0 siblings, 1 reply; 4+ messages in thread
From: Ludovic Courtès @ 2018-08-20 10:21 UTC (permalink / raw)
To: HiPhish; +Cc: 32473-done
Hello Hiphish,
HiPhish <hiphish@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’.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#32473: Broken menu entry in manual, section 4.1
2018-08-20 10:21 ` Ludovic Courtès
@ 2018-08-21 10:56 ` HiPhish
2018-08-21 21:35 ` Ludovic Courtès
0 siblings, 1 reply; 4+ messages in thread
From: HiPhish @ 2018-08-21 10:56 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 32473
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#32473: Broken menu entry in manual, section 4.1
2018-08-21 10:56 ` HiPhish
@ 2018-08-21 21:35 ` Ludovic Courtès
0 siblings, 0 replies; 4+ messages in thread
From: Ludovic Courtès @ 2018-08-21 21:35 UTC (permalink / raw)
To: HiPhish; +Cc: 32473
HiPhish <hiphish@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’.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-08-21 21:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-08-19 12:39 bug#32473: Broken menu entry in manual, section 4.1 HiPhish
2018-08-20 10:21 ` Ludovic Courtès
2018-08-21 10:56 ` HiPhish
2018-08-21 21:35 ` Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).