public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo beeping at me!
Date: Sat, 27 Nov 2004 03:03:52 +0900	[thread overview]
Message-ID: <20041126180351.GA11093@lion.gg3.net> (raw)
In-Reply-To: <20041126101734.59070a9a@snowdrop.home>

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

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:
> | maillog: 25/11/2004-19:19:27(+0000): Ed Grimm types
> | > On Thu, 25 Nov 2004, Georgi Georgiev wrote:
> | > 
> | > If you really think that in-line docs are ugly, use vim(1), and
> | > automagically fold them out of your view (:help foldexpr, although
> | > this can be set to happen in the eclass syntax file).  I suspect
> | > that most of the people who only occasionally work with the
> | > eclasses, and those who are just starting to use the eclasses, would
> | > find them more useful than ugly.
> | 
> | 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

> Here's another possibility:
> 
> # {{{ doc
> # whatever format we decide upon
> # blah blah blah
> # }}}
> 
> Doesn't screw up normal comments, really easy to find and process, easy
> to turn into folds in the editor :)

Sounds great. Now all that's left is to agree upon the format and write
the converter. Oh, and my favorite -- a GLEP maybe? (no, I'm not
sarcastic; just in a good mood ;) ).

-- 
 )   Georgi Georgiev    ) Hi! I'm Larry. This is my brother Bob, and    )
(     chutz@gg3.net    (  this is my other brother Jimbo. We thought   (
 )  +81(90)6266-1163    ) you might like to know the names of your      )
(  ------------------- (  assailants.                                  (

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-26 18:04 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 [this message]
2004-11-26 18:45                                 ` Dan Meltzer
2004-11-26 19:17                                   ` Ciaran McCreesh
2004-11-26 23:55                                 ` Ed Grimm

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=20041126180351.GA11093@lion.gg3.net \
    --to=chutz@gg3.net \
    --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