From: Gavin Smith <gavinsmith0123@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Vincent Belaïche" <Vincent.b.1@hotmail.fr>, 18308@debbugs.gnu.org
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Fri, 22 Aug 2014 18:56:07 +0100 [thread overview]
Message-ID: <CAKPWYQ2GwtNpQfQVJSssA0mV6hx7CMgqctW26LwOPRN5JdPq3Q@mail.gmail.com> (raw)
In-Reply-To: <83d2btav4x.fsf@gnu.org>
On Fri, Aug 22, 2014 at 7:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Emacs already does all that, of course. Just not in the case of the
> menu entries, where the node names are not expected to span more than
> one line.
>
>> So, on second thoughts, I am thinking in the end that for consistency,
>> the info viewer not only should, but also _must_ be corrected.
>
> As I said, maybe. But the fact is that the _Texinfo_source_ of the
> Texinfo manual uses different amounts of blanks in this node's name.
> So line breaking and filling in the Info file is not the issue here.
>
I have deleted an extra space in the menu entries in question in the
Texinfo manual, and following these links works in emacs Info now. I
agree that whitespace normalization is not essential in menu entries.
next prev parent reply other threads:[~2014-08-22 17:56 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
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 [this message]
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=CAKPWYQ2GwtNpQfQVJSssA0mV6hx7CMgqctW26LwOPRN5JdPq3Q@mail.gmail.com \
--to=gavinsmith0123@gmail.com \
--cc=18308@debbugs.gnu.org \
--cc=Vincent.b.1@hotmail.fr \
--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 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).