From: Steve Youngs <steve@youngs.au.com>
Subject: Re: nnml article filenames
Date: Mon, 31 Oct 2005 07:30:01 GMT [thread overview]
Message-ID: <microsoft-free.87pspmrvw8.fsf@youngs.au.com> (raw)
In-Reply-To: <u3bmi45lg.fsf@cisco.com>
* Pranav K Tiwari <jpranav@cisco.com> writes:
> Steve Youngs <steve@youngs.au.com> writes:
>> * Pranav K Tiwari <jpranav@cisco.com> writes:
>>
>> > To allow desktop search programs go through nnml articles, I would
>> > like to give an extension like .xyz, and tell these programs to
>> > treat these files like email.
>>
>> I think this is the wrong approach. Instead of modifying the
>> filenames to suit the search program, find a way to make the search
>> program work properly.
>>
>> It's really not that difficult, see...
>>
>> $ find <nnmldir> -type f -regex '^.*[0-9]+$'
>>
> The question is not about 'finding' these files, but about
> associating a 'type' with the file.
But if you can find them, there's really no point in associating a
"type" to them.
$ find <nnmldir> -type f -regex '^.*[0-9]+$' | \
xargs some_app_needing_mail_files_as_input
> Most indexing programs (google/yahoo/microsoft desktop search
> engines, X1) rely on file extensions to determine the filetype,
> and then index the contens of the file accordingly. It'll be good
> if they could deal with files with no extensions, but they don't
> (afaik).
Yes they do. For example:
<http://homepage.mac.com/pauljlucas/software/swish/>
> So - with that in mind, the easiest way would be to change the way gnus
> nnml stores files, or write another backend that allows changing
> filenames.
Maybe you should say what it is exactly that you want to do with your
nnml files.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Te audire no possum. |
| Musa sapientum fixa est in aure. |
|----------------------------------<steve@youngs.au.com>---|
next prev parent reply other threads:[~2005-10-31 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 12:05 Pranav K. Tiwari
2005-10-28 13:30 ` Steve Youngs
2005-10-31 5:29 ` Pranav K. Tiwari
2005-10-31 7:30 ` Steve Youngs [this message]
2005-10-31 9:13 ` Pranav K. Tiwari
2006-04-20 8:59 ` Pranav K. Tiwari
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=microsoft-free.87pspmrvw8.fsf@youngs.au.com \
--to=steve@youngs.au.com \
/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;
as well as URLs for NNTP newsgroup(s).