From: Juri Linkov <juri@jurta.org>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 10784@debbugs.gnu.org
Subject: bug#10784: 23.1; info doesn't follow link in Bison TOC
Date: Sun, 12 Feb 2012 23:15:49 +0200 [thread overview]
Message-ID: <87fweflpmi.fsf@mail.jurta.org> (raw)
In-Reply-To: <m3y5safinr.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Fri, 10 Feb 2012 22:06:00 +0000")
> | [tim@passepartout ~/src/emacs]$ zgrep 'Secure\?' /usr/share/info/bison.info.gz
> | * Secure? Conform?:: Is Bison POSIX safe?
> | * Secure? Conform?:: Is Bison POSIX safe?
> | File: bison.info, Node: Multiple start-symbols, Next: Secure? Conform?, Prev: Implementing Gotos/Loops, Up: FAQ
> | File: bison.info, Node: Secure? Conform?, Next: I can't build Bison, Prev: Multiple start-symbols, Up: FAQ
> | 11.6 Secure? Conform?
> | File: bison.info, Node: I can't build Bison, Next: Where can I find help?, Prev: Secure? Conform?, Up: FAQ
> | Node: Secure? Conform?364602
> | [tim@passepartout ~/src/emacs]$
>
> Note the one vs. two spaces between "Secure?" and "Con-
> form?". The link works with info (GNU texinfo) 4.13. The
> bug is also present in a Emacs snapshot from early February.
Does this mean that info (GNU texinfo) 4.13 treats a sequence of spaces
in the names as one space character? If yes, should info.el do the same
with a patch like this:
=== modified file 'lisp/info.el'
--- lisp/info.el 2012-02-12 20:24:02 +0000
+++ lisp/info.el 2012-02-12 21:11:33 +0000
@@ -1025,7 +1025,9 @@ (defun Info-find-node-2 (filename nodena
(let ((guesspos (point-min))
(regexp (concat "\\(Node:\\|Ref:\\) *\\("
(if (stringp nodename)
- (regexp-quote nodename)
+ (mapconcat 'regexp-quote
+ (split-string nodename " +" t)
+ " +")
"")
"\\) *[,\t\n\177]")))
next prev parent reply other threads:[~2012-02-12 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 22:06 bug#10784: 23.1; info doesn't follow link in Bison TOC Tim Landscheidt
2012-02-12 21:15 ` Juri Linkov [this message]
2012-02-13 17:15 ` Eli Zaretskii
2020-09-14 11:50 ` Lars Ingebrigtsen
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=87fweflpmi.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10784@debbugs.gnu.org \
--cc=tim@tim-landscheidt.de \
/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.