From: jidanni@jidanni.org
To: juri@jurta.org
Cc: 5568@debbugs.gnu.org
Subject: bug#5568: Man-follow-manual-reference vs. perl man pages
Date: Sun, 14 Feb 2010 09:08:35 +0800 [thread overview]
Message-ID: <87ljewmxnw.fsf@jidanni.org> (raw)
In-Reply-To: <87tytnc577.fsf@jidanni.org>
JL> BTW, I think we should handle HTTP links because they have a definite regexp
JL> that we can match.
Hmm, maybe anything with :: in them too. However I suppose those perl guys
can't be bothered to put the
$ man encode|sed 's/ .*//;q'
Encode(3perl)
or some other hint there in the SEE ALSOs. I would remind them but I'm
banned for life from mailing *@perl.org because of my crabby personality
or something.
prev parent reply other threads:[~2010-02-14 1:08 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
2010-02-13 20:19 ` jidanni
2010-02-14 0:30 ` Juri Linkov
2010-02-14 1:08 ` jidanni [this message]
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=87ljewmxnw.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=5568@debbugs.gnu.org \
--cc=juri@jurta.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).