From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Cc: mcbrides9@comcast.net
Subject: Re: [gentoo-user] Documentation Index
Date: Sat, 30 Dec 2006 23:04:24 -0500 [thread overview]
Message-ID: <20061230230424.78745540@osage.osagesoftware.com> (raw)
In-Reply-To: <200612302220.18268.mcbrides9@comcast.net>
On Sat, 30 Dec 2006 22:20:18 -0500
Jerry McBride wrote:
> On Saturday 30 December 2006 19:03, Kevin O'Gorman wrote:
> > There's a lot of HTML documentation on my computer, but it's
> > wonderfully hard to find and use compared to man pages
> > because it's not indexed.
> >
> > So I started building a Perl script to create a top-level
> > HTML index page automatically from the .html files it
> > finds lying around. I started with just the contents of
> > /usr/share/doc.
> >
> > Before I go too much farther, I thought I'd ask if anyone knows
> > of an existing product (that is surely more refined than
> > this little starter gizmo I've got so frar) that does the
> > same or similar thing?
> >
> > If not, are there any other places where generally useful
> > HTML might be hiding?
> >
>
> I've been doing a similar project using python. I scan the entire
> filesystem for html, pdf and chm files. Once found, I grab matching
> portage names and build a master html index for use with apache...
>
> Nice to know that someone else has the desire for handy document
> indexes...
I, for one, would be interested in seeing a copy of your script :->
David
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-31 4:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 0:03 [gentoo-user] Documentation Index Kevin O'Gorman
2006-12-31 0:19 ` Graham Murray
2006-12-31 3:20 ` Jerry McBride
2006-12-31 4:04 ` David Relson [this message]
2006-12-31 5:00 ` Kevin O'Gorman
2006-12-31 17:38 ` Jerry McBride
2007-01-01 1:28 ` Kevin O'Gorman
2007-01-01 11:43 ` Neil Bothwick
2007-01-01 18:18 ` Jerry McBride
2006-12-31 10:50 ` Mick
2006-12-31 10:57 ` iddqd
2006-12-31 12:39 ` Kent Fredric
2006-12-31 12:46 ` Mick
2007-01-04 15:13 ` Etaoin Shrdlu
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=20061230230424.78745540@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=mcbrides9@comcast.net \
/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