From: "Vincent Belaïche" <Vincent.b.1@hotmail.fr>
To: Eli Zaretskii <Eliz@gnu.org>
Cc: 18308@debbugs.gnu.org
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Thu, 21 Aug 2014 18:30:59 +0200 [thread overview]
Message-ID: <8038cp4xfg.fsf@gmail.com> (raw)
In-Reply-To: <80bnre44fc.fsf@gmail.com>
Resent With cc to 18308@debbugs.gnu.org
Feedback inserted below...
----------------------------------------
> Date: Thu, 21 Aug 2014 17:12:13 +0300
> From: eliz@gnu.org
> Subject: Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
> To: vincent.b.1@hotmail.fr
> CC: 18308@debbugs.gnu.org
>
> > From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> > Date: Thu, 21 Aug 2014 10:45:11 +0200
> > Cc: Vincent Belaïche <vincent.b.1@hotmail.fr>
> >
> > In texinfo manual, info node `(texinfo) Breaks', if I set pointer on
> > third menu entry and type RET, the I get message:
> >
> > user-error: No such node or anchor: @- @hyphenation
>
> This is not an Emacs bug, it's a bug in the Texinfo manual. For some
> reason, it sometimes refers to this node as "@- @hyphenation" (with 2
> spaces), and sometimes as "@- @hyphenation" (with only 1 space). The
> menu uses the former, while the node name uses the latter. So Emacs
> cannot find the node.
>
> > However, if I type '3', then I go to the wanted node.
>
> That's because the command bound to '3' normalizes the whitespace in
> the node name. I don't know why it does that, but that code exists
> since about forever.
>
> Maybe we could consider normalizing the whitespace in the 1st case as
> well, but that's just a work around for a buggy manual.
I would not say that this is a bug in the manual --- manuals are written
by human beings, and human beings are living creatures, just like bugs
are ;-) .
Rather, I think that this is a bug in the texinfo info compiler that
should:
1) produce some warning message, as a matter of fact the manual is not
consistent with info node `(texinfo) Node Line Requirements' --- see
below why
2) collapse multiple spaces to a single space in node names as the info
file is produced.
In info node "(texinfo) Node Line Requirements", there is this
statement:
-----------------------------------------------------------------------
Spaces before and after names on the '@node' line are ignored.
Multiple whitespace characters "inside" a name are collapsed to a
single space. For example:
@node foo bar,
@node foo bar ,
@node foo bar,
@node foo bar ,
all define the same node, namely 'foo bar'. References to the node
should all use that name, with no leading or trailing spaces a
single internal space.
-----------------------------------------------------------------------
It seems that there is a typo in this node and the end of last sentence
should read: "with no leading or trailing spaces *AND* a single internal
space". Anyway, because the menu entry is a REFERENCE to the node, then
it should use this name with a single internal space. Because it does
not, the manual is not conformant to this spec.
So, I think that you treate the EMACS info viewer bug as you like ---
either close it, or think that you should make the info viewer more
robust by collapsing multiple internal spaces to a single space like the
'3' command does. My personal feeling is that you should robustify the
info viewer.
On my side I will open a bug Texinfo project to refer to this one and
ask for compiler to handle point 1) and 2) above and correct the typo in
the manual.
Vincent.
next prev parent reply other threads:[~2014-08-21 16:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:45 bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation' Vincent Belaïche
2014-08-21 14:12 ` Eli Zaretskii
2014-08-21 16:30 ` Vincent Belaïche [this message]
2014-08-21 22:23 ` Vincent Belaïche
2014-08-22 6:36 ` Eli Zaretskii
2014-08-22 17:17 ` Richard Stallman
2014-08-22 20:12 ` Gavin Smith
2014-08-22 20:57 ` Eli Zaretskii
2014-08-23 19:44 ` Richard Stallman
2014-08-24 14:05 ` Stefan Monnier
2014-08-24 23:41 ` Richard Stallman
2014-08-25 15:05 ` Stefan Monnier
2014-08-25 19:11 ` Richard Stallman
2014-08-25 2:07 ` Tom Tromey
2014-08-25 19:10 ` Richard Stallman
2014-08-22 17:56 ` Gavin Smith
2014-08-26 15:58 ` Glenn Morris
2014-08-22 13:01 ` Vincent Belaïche
2014-08-22 13:36 ` Eli Zaretskii
2014-08-22 22:04 ` Vincent Belaïche
2014-08-22 22:09 ` Glenn Morris
2014-08-31 22:37 ` Gavin Smith
[not found] ` <CAKPWYQ2r6y7spGnwU+34BQDMYRikEGoROP0BAJ5mLR0g4d7jTg@mail.gmail.com>
2014-09-01 19:40 ` Vincent Belaïche
2014-09-01 21:37 ` Gavin Smith
2014-09-01 21:53 ` Karl Berry
[not found] ` <201409012153.s81LrtTi021549@freefriends.org>
2014-09-02 21:44 ` Vincent Belaïche
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8038cp4xfg.fsf@gmail.com \
--to=vincent.b.1@hotmail.fr \
--cc=18308@debbugs.gnu.org \
--cc=Eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.