From: Simon Cozens <simon@simon-cozens.org>
To: notmuch <notmuch@notmuchmail.org>
Subject: Indexing without files and directories
Date: Wed, 27 Jan 2010 14:12:50 +0000 [thread overview]
Message-ID: <4B6049E2.2030209@simon-cozens.org> (raw)
Hi all,
I don't want to throw a spanner in the works, but I am intending to use
notmuch for indexing in a scenario where the email doesn't hit the disk
- the notmuch model seems to rely pretty heavily on directories and
files but I'm working with email being delivered to a script for
indexing and then stored into a database. So far I've been hacking it by
feeding "/dev/stdin" as a filename but that leads to interesting fun
when I forget and try to access something via a notmuch_message object.
With all this talk of a new object store, can I put in a plea for - at
least at the API level - some way of indexing based on a user-defined
location identifier? (In my case, a database row ID.)
Thanks,
Simon
reply other threads:[~2010-01-27 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B6049E2.2030209@simon-cozens.org \
--to=simon@simon-cozens.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).