GNU bug report logs -
#9824
Info fails to follow multi-line links to manuals with dots
Previous Next
Reported by: Juri Linkov <juri <at> jurta.org>
Date: Fri, 21 Oct 2011 14:13:01 UTC
Severity: normal
Done: Juri Linkov <juri <at> jurta.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 9824 in the body.
You can then email your comments to 9824 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#9824
; Package
emacs
.
(Fri, 21 Oct 2011 14:13:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Juri Linkov <juri <at> jurta.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 21 Oct 2011 14:13:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
For example, clicking on the following link fails to navigate to another
Info manual:
languages, are documented in a separate manual. *Note Introduction:
(gccint-4.4)Top.
because a regexp for leading space in `Info-following-node-name-re'
doesn't take into account multi-line case.
Links to manuals without dots in the file name currently work
just by accident, e.g. clicking on:
are performed by running the function. *Note What Is a Function:
(elisp)What Is a Function.
works because the regexp for unallowed chars in node names
doesn't contain parens (but contains dots) and matches everything
including file names (without dots).
This is wrong but I hesitate to make the regexp more restrictive
by disallowing parens in node names because Info currently using
regexp matching extensively is very brittle.
The following patch makes the regexp for leading space more permissive
by allowing newlines in leading space:
=== modified file 'lisp/info.el'
--- lisp/info.el 2011-09-24 19:18:43 +0000
+++ lisp/info.el 2011-10-21 14:10:04 +0000
@@ -2020,7 +2020,7 @@ (defun Info-following-node-name-re (&opt
Submatch 2 if non-nil is the parenthesized file name part of the node name.
Submatch 3 is the local part of the node name.
End of submatch 0, 1, and 3 are the same, so you can safely concat."
- (concat "[ \t]*" ;Skip leading space.
+ (concat "[ \t\n]*" ;Skip leading space.
"\\(\\(([^)]+)\\)?" ;Node name can start with a file name.
"\\([" (or allowedchars "^,\t\n") "]*" ;Any number of allowed chars.
"[" (or allowedchars "^,\t\n") " ]" ;The last char can't be a space.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#9824
; Package
emacs
.
(Fri, 21 Oct 2011 17:44:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 9824 <at> debbugs.gnu.org (full text, mbox):
> The following patch makes the regexp for leading space more permissive
> by allowing newlines in leading space:
Looks acceptable,
Stefan
Reply sent
to
Juri Linkov <juri <at> jurta.org>
:
You have taken responsibility.
(Mon, 24 Oct 2011 05:53:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Juri Linkov <juri <at> jurta.org>
:
bug acknowledged by developer.
(Mon, 24 Oct 2011 05:53:03 GMT)
Full text and
rfc822 format available.
Message #13 received at 9824-done <at> debbugs.gnu.org (full text, mbox):
>> The following patch makes the regexp for leading space more permissive
>> by allowing newlines in leading space:
>
> Looks acceptable,
Installed.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 21 Nov 2011 12:24:02 GMT)
Full text and
rfc822 format available.
This bug report was last modified 12 years and 168 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.