From: Juri Linkov <juri@jurta.org>
To: jidanni@jidanni.org
Cc: 5568@debbugs.gnu.org
Subject: bug#5568: Man-follow-manual-reference vs. perl man pages
Date: Fri, 12 Feb 2010 21:19:10 +0200 [thread overview]
Message-ID: <874olmcqhl.fsf@mail.jurta.org> (raw)
In-Reply-To: <87tytnc577.fsf@jidanni.org> (jidanni@jidanni.org's message of "Fri, 12 Feb 2010 14:56:44 +0800")
> Many man pages have SEE ALSOs like
>
> SEE ALSO
> XML::Parser::Lite.
> perl v5.10.0 2009-08-23 XML::Parser::Lite::Tree(3pm)
>
> However Man-follow-manual-reference can't figure out that kind of
> SEE ALSO item.
The references in this SEE ALSO section are in a non-standard format.
A reference should be a word followed by the section name in parentheses.
So these man pages should write references in the format
"XML::Parser::Lite(3pm)".
Of course, you can get what you want with the following patch:
=== modified file 'lisp/man.el'
--- lisp/man.el 2010-02-11 20:57:10 +0000
+++ lisp/man.el 2010-02-12 19:18:50 +0000
@@ -1135,7 +1135,7 @@ (defun Man-highlight-references (&option
(Man-highlight-references0 nil Man-apropos-regexp 1
'Man-default-man-entry
(or xref-man-type 'Man-xref-man-page)))
- (Man-highlight-references0 Man-see-also-regexp Man-reference-regexp 1
+ (Man-highlight-references0 Man-see-also-regexp Man-hyphenated-reference-regexp 1
'Man-default-man-entry
(or xref-man-type 'Man-xref-man-page))
(Man-highlight-references0 Man-synopsis-regexp Man-header-regexp 0 2
But it will also highlight every word in those SEE ALSO sections
that have lengthy text in several paragraphs. Look for example
`M-x man XML::Twig RET' - there are 60 lines in the SEE ALSO section
where all words will be highlighted as a reference!
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2010-02-12 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 6:56 bug#5568: Man-follow-manual-reference vs. perl man pages jidanni
2010-02-12 19:19 ` Juri Linkov [this message]
2010-02-13 20:19 ` jidanni
2010-02-14 0:30 ` Juri Linkov
2010-02-14 1:08 ` jidanni
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=874olmcqhl.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=5568@debbugs.gnu.org \
--cc=jidanni@jidanni.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).