unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <Vincent.b.1@hotmail.fr>
To: Eli Zaretskii <Eliz@gnu.org>,    Gavin Smith <gavinsmith0123@gmail.com>
Cc: 18308@debbugs.gnu.org
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Fri, 22 Aug 2014 00:23:44 +0200	[thread overview]
Message-ID: <80wqa132j3.fsf@gmail.com> (raw)
In-Reply-To: <80bnre44fc.fsf@gmail.com>

Dear Eli et alii,

Looping also through Gavin.

For your information I have filed these two bugs to texinfo.

http://savannah.gnu.org/bugs/index.php?43045
http://savannah.gnu.org/bugs/index.php?43042

During the discussion on bug-texinfo@gnu.org concerning texinfo
bug#43042, I received the following comment from Gavin Smith:

> I don't think it is actually the case that references should use
> normalized whitespace. For example, there is the following in the bash
> manual, node "Shell Operation":
>
>   3. Parses the tokens into simple and compound commands (*note Shell
>      Commands::).
>
> Here we have a newline and initial line indent in the middle of the
> node name "Shell Commands", but following this cross-reference works
> fine.

I a nutshell, there are cases of node references where the info viewer
is not bothered by internal multiple spaces (this cross reference inside
bash manual), and other cases where the info viewer cannot handle it
(the case of node "(texinfo) @- @hyphenation" pointer in menu entry of
upper node).

So, on second thoughts, I am thinking in the end that for consistency,
the info viewer not only should, but also _must_ be corrected.

I am even speculating that in the case of the manual menu entry,
probably it was intentional to put more spaces for the entry to read
better (as @- and @hyphenation are two different commands, isn't it a
good idea to put a little more space between them).

Maybe the texinfo manual could also be corected as follows (with two
spaces in label, and one space in node pointer):

* @t{@@-  @@hyphenation}: @t{@@- @@hyphenation}.            Helping @TeX{} with hyphenation points.

ie by using the

* LABEL: NODE. TITLE

construct instead of the

* NODE:: TITLE

construct. Well... this is not your business, but if Gabin had read this
email up to this point, he may have an opinion.

VBR,
   Vincent.













  parent reply	other threads:[~2014-08-21 22:23 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
2014-08-21 22:23 ` Vincent Belaïche [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80wqa132j3.fsf@gmail.com \
    --to=vincent.b.1@hotmail.fr \
    --cc=18308@debbugs.gnu.org \
    --cc=Eliz@gnu.org \
    --cc=gavinsmith0123@gmail.com \
    /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/emacs.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).