> From: Tim Landscheidt <[email protected]> > Date: Sun, 12 Feb 2012 22:03:14 +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?".
I could argue that using 2 sentences with 2 spaces between them as a node name is a minor bug in the Bison manual (which, btw, is still not fixed in the latest version 2.5). > This led to the question in > http://permalink.gmane.org/gmane.emacs.bugs/56847: You mean, [email protected] ;-) > | Does this mean that info (GNU texinfo) 4.13 treats a sequence of spaces > | in the names as one space character? > > So I turn to the wisdom gathered here :-). As I responded there, the answer is YES. The Info reader canonicalizes the whitespace in a node name before it uses it for search, and it also searches in a way that ignores excess whitespace in the target string.
