From: HiPhish <hiphish@posteo.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32473@debbugs.gnu.org
Subject: bug#32473: Broken menu entry in manual, section 4.1
Date: Tue, 21 Aug 2018 12:56:40 +0200 [thread overview]
Message-ID: <3105889.ghd2rdMcOe@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87k1olfiek.fsf@gnu.org>
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.
next prev parent reply other threads:[~2018-08-21 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-08-21 21:35 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3105889.ghd2rdMcOe@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=32473@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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/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).