From: Ed Grimm <paranoid@gentoo.evolution.tgape.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo beeping at me!
Date: Fri, 26 Nov 2004 23:55:14 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.60.0411262342120.5557@mbeq.rq.iarg> (raw)
In-Reply-To: <20041126180351.GA11093@lion.gg3.net>
On Sat, 27 Nov 2004, Georgi Georgiev wrote:
> maillog: 26/11/2004-10:17:34(+0000): Ciaran McCreesh types
>> On Fri, 26 Nov 2004 11:25:10 +0900 Georgi Georgiev <chutz@gg3.net>
>> wrote:
>>| I have nothing against in-line docs in general. I simply had trouble
>>| imagining it in the bash case.
>>|
>>| What about using perldoc itself? Simply prepend every doc line with a
>>| '#', then run
>>|
>>| awk '/^#/ { sub("#",""); print }
>>
>> In bash? How would that work?
>
> I imagined
>
> #=item blah blah
> # more POD
> # and more
> # and more
> #=cut
Note that Pod::Parser has a method (preprocess_line) which one could
utilize to do the strip without requiring an awk pre-processing step.
That being said, as the pod reformatting packages are written as
Pod::Parser subclasses, I'm not certain if it could be utilized
gracefully without limiting the potential output formats. It may be
possible to make a generic class which does the magic, and a magical
subclass of that class which inherits from both it and a particular
formatting subclass, such that preprocess_line comes from the generic
class, and everything else comes from the formatting subclass.
Ed
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-11-26 23:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 1:43 [gentoo-dev] Gentoo beeping at me! Roman Gaufman
2004-11-23 1:51 ` Mike Frysinger
[not found] ` <E86D9DE1-3D06-11D9-A6F4-000A95D3E704@gentoo.org>
2004-11-23 4:33 ` Mike Frysinger
2004-11-23 4:38 ` Lina Pezzella
2004-11-23 4:45 ` Mike Frysinger
2004-11-23 7:38 ` Daniel Armyr
2004-11-23 8:14 ` Ciaran McCreesh
2004-11-23 14:38 ` Roman Gaufman
2004-11-23 15:55 ` Hasan Khalil
2004-11-23 16:09 ` Ciaran McCreesh
2004-11-24 10:14 ` Aaron Walker
2004-11-23 16:20 ` Chris Gianelloni
2004-11-23 23:26 ` Dan Meltzer
2004-11-24 2:15 ` Chris Gianelloni
2004-11-24 10:08 ` Aaron Walker
[not found] ` <46059ce1041123200452e69415@mail.gmail.com>
2004-11-24 13:44 ` Chris Gianelloni
2004-11-24 20:10 ` Benjamin Schindler
2004-11-25 9:44 ` Georgi Georgiev
2004-11-25 19:19 ` Ed Grimm
2004-11-25 20:02 ` Ciaran McCreesh
2004-11-26 2:25 ` Georgi Georgiev
2004-11-26 10:17 ` Ciaran McCreesh
2004-11-26 18:03 ` Georgi Georgiev
2004-11-26 18:45 ` Dan Meltzer
2004-11-26 19:17 ` Ciaran McCreesh
2004-11-26 23:55 ` Ed Grimm [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.60.0411262342120.5557@mbeq.rq.iarg \
--to=paranoid@gentoo.evolution.tgape.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox