From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19620 invoked from network); 26 Nov 2004 02:25:30 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 26 Nov 2004 02:25:30 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CXVne-0003GA-RM for arch-gentoo-dev@lists.gentoo.org; Fri, 26 Nov 2004 02:25:30 +0000 Received: (qmail 12735 invoked by uid 89); 26 Nov 2004 02:25:30 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 12853 invoked from network); 26 Nov 2004 02:25:29 +0000 Date: Fri, 26 Nov 2004 11:25:10 +0900 From: Georgi Georgiev To: gentoo-dev@lists.gentoo.org Message-ID: <20041126022509.GA26935@ols-dell.iic.hokudai.ac.jp> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <200411222345.14487.vapier@gentoo.org> <3908185A3D2C144E9FAD070D2727FFD81716A9@PERIMAIL.perimed.priv> <921ad39e04112306381595bc8a@mail.gmail.com> <1049C878-3D68-11D9-9250-000A958238BC@gentoo.org> <1101226835.9000.39.camel@cgianelloni.nuvox.net> <46059ce104112315265d557064@mail.gmail.com> <1101327015.9848.5.camel@io> <20041125094444.GA13530@lion.gg3.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: [gentoo-dev] Gentoo beeping at me! X-Archives-Salt: 9a264733-b4e3-4a43-a2ba-9a2cba1d854a X-Archives-Hash: 2ae1b6bda3ecefeacc473fa2c3e52623 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 } on the file and pass this output to perldoc. This has the advantage of having the necessary tools at hand already, so that no extra tools are needed for the docs. -- \ Georgi Georgiev \ A lot of people I know believe in positive \ / chutz@gg3.net / thinking, and so do I. I believe / \ +81(90)6266-1163 \ everything positively stinks. ti -- Lew \ / ------------------- / Col / -- gentoo-dev@gentoo.org mailing list