GNU logs - #10784, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#10784: 23.1; info doesn't follow link in Bison TOC
Resent-From: Tim Landscheidt <tim@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Fri, 10 Feb 2012 22:08:02 +0000
Resent-Message-ID: <handler.10784.B.132891166332164 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 10784 <at> debbugs.gnu.org
From: Tim Landscheidt <tim@HIDDEN>
Organization: <URI:http://www.tim-landscheidt.de/>
Date: Fri, 10 Feb 2012 22:06:00 +0000
Message-ID: <m3y5safinr.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

- (info "(bison)")   ;; version 2.4.1
- search for TOC item "Secure?  Conform?"
- press RET
- => "No such node or anchor: Secure?  Conform?"

(Probably) relevant bits from the info file:

| [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.


In GNU Emacs 23.1.1 (i386-redhat-linux-gnu, GTK+ Version 2.16.6)
 of 2010-04-01 on x86-01.phx2.fedoraproject.org
Windowing system distributor `The X.Org Foundation', version 11.0.10603901
configured using `configure  '--build=i386-redhat-linux-gnu' '--host=i386-redhat-linux-gnu' '--target=i586-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--localstatedir=/var' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-dbus' '--with-gif' '--with-jpeg' '--with-png' '--with-rsvg' '--with-tiff' '--with-xft' '--with-xpm' '--with-x-toolkit=gtk' 'build_alias=i386-redhat-linux-gnu' 'host_alias=i386-redhat-linux-gnu' 'target_alias=i586-redhat-linux-gnu' 'CFLAGS=-DMAIL_USE_LOCKF -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i586 -mtune=generic -fasynchronous-unwind-tables''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: de_DE.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Tim Landscheidt <tim@HIDDEN>
Subject: bug#10784: Acknowledgement (23.1; info doesn't follow link in
 Bison TOC)
Message-ID: <handler.10784.B.132891166332164.ack <at> debbugs.gnu.org>
References: <m3y5safinr.fsf@HIDDEN>
X-Gnu-PR-Message: ack 10784
X-Gnu-PR-Package: emacs
Reply-To: 10784 <at> debbugs.gnu.org
Date: Fri, 10 Feb 2012 22:08:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 10784 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
10784: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D10784
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#10784: 23.1; info doesn't follow link in Bison TOC
Resent-From: Juri Linkov <juri@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sun, 12 Feb 2012 21:25:01 +0000
Resent-Message-ID: <handler.10784.B10784.132908186110618 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Tim Landscheidt <tim@HIDDEN>
Cc: 10784 <at> debbugs.gnu.org
From: Juri Linkov <juri@HIDDEN>
Organization: JURTA
References: <m3y5safinr.fsf@HIDDEN>
Date: Sun, 12 Feb 2012 23:15:49 +0200
In-Reply-To: <m3y5safinr.fsf@HIDDEN> (Tim
	Landscheidt's message of "Fri, 10 Feb 2012 22:06:00 +0000")
Message-ID: <87fweflpmi.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.93 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

> | [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]")))

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#10784: 23.1; info doesn't follow link in Bison TOC
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 13 Feb 2012 17:18:01 +0000
Resent-Message-ID: <handler.10784.B10784.132915344710748 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Juri Linkov <juri@HIDDEN>
Cc: 10784 <at> debbugs.gnu.org, tim@HIDDEN
Reply-To: Eli Zaretskii <eliz@HIDDEN>
Date: Mon, 13 Feb 2012 19:15:30 +0200
From: Eli Zaretskii <eliz@HIDDEN>
In-reply-to: <87fweflpmi.fsf@HIDDEN>
Message-id: <83r4xyy7rh.fsf@HIDDEN>
References: <m3y5safinr.fsf@HIDDEN>
	<87fweflpmi.fsf@HIDDEN>
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

> From: Juri Linkov <juri@HIDDEN>
> Date: Sun, 12 Feb 2012 23:15:49 +0200
> Cc: 10784 <at> debbugs.gnu.org
> 
> > | [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?

The stand-alone Info reader always, since day one, canonicalized any
whitespace in node names.

> If yes, should info.el do the same

Yes, it definitely should.  And it already does, just not
consistently.  E.g., if, instead of typing RET on that menu line, you
type "m RET", you get to the right node without any error messages.

> 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]")))

I'm not sure this is TRT.  First, we should convert _any_ whitespace,
not just a sequence of SPC characters, to a single SPC.  Second, I
think it would be better to have a single function for this job and
call it from all the places that need to produce a canonical node
name.  I see at least one other place (`Info-extract-menu-node-name')
where we need to do the same, and possibly one more in
`Info-fontify-node'.  If we do this in each place individually, we
will have inconsistent bugs, whereas we want _consistent_ bugs ;-)

Finally, I think the right place to do this is in Info-find-node, not
Info-find-node-2.

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.