From: Johannes Kulick <johannes@mailless.org>
To: Austin Clements <amdragon@MIT.EDU>,
Cc: notmuch@notmuchmail.org
Subject: Re: Feature proposal: OUTPUT_AUTHOR format
Date: Tue, 27 Aug 2013 16:06:54 +0200 [thread overview]
Message-ID: <20130827140654.31336.307@quirm.robotics.tu-berlin.de> (raw)
In-Reply-To: <20130827134723.GQ13257@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
> What's the advantage to adding this to the library? Why not just
> notmuch_query_search_messages, iterate over the messages and use
> notmuch_message_get_header(msg, "from") to accumulate the author
> information, and then output that? Unless I'm overlooking something
> (which is possible), there are no algorithmic advantages to doing this
> in the library.
The view I have in mind would look something like:
John Doe (1234 msg)
|- first thread subject
|- second thread subject
|- third thread subject
Jane Doe (234 msg)
|- first thread subject
|- second thread subject
|- third thread subject
...
The problem is, that if I want to have a list of all authors in the database I'd
have to iterate over all messages (naively implemented, whenever I render the
view, or I somehow have to persistently store this list and update it on a
regular basis), whereas the notmuch database already has this information but
doesn't reveal if I'm not overlooking something. To do a
notmuch_query_search_messages I'd have to know what to search for, whereas a
notmuch_database_get_all_authors would give me exactly what I'm looking for in
short time since it is already indexed by xapian.
Best,
Johannes
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAABAgAGBQJSHLJ+AAoJEBiRJNhhEUhOYrQH/2tmIopguoNlnepIgcI52JRY
Yuis52XGbverFYBoZEgeI36DSQghlNeBYakYcWYmHf9a6ZkxVtWR6arrXp3A1pCb
eSm4ZqDowA1qTaAh9mMlIGWwRkSAS5meJulf9Yhmnv353AJsZvrJz8283bUrULjM
HhcJ/Uh7KF1gN1arfOxwsTtQNXjrPpUd1E0voNYERCGhX5cqLevrkJdrzUEv6+PF
lSl2b3701J8q86Pphm0Trr2AWEdMyZxMXJpOeF2+9l8vrTB1KAEhsyPO+7V2YfUx
sEoncvEGAvdRlK5KmlKp/Ql5HUwMUv+96nl1I6TMg2BWyHhxjgZHPmxyqI8ofkk=
=tIcK
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-08-27 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130825101308.27461.57489@quirm.robotics.tu-berlin.de>
2013-08-26 22:22 ` Feature proposal: OUTPUT_AUTHOR format Johannes Kulick
2013-08-27 0:27 ` David Bremner
2013-08-27 5:21 ` Jani Nikula
2013-08-27 11:50 ` Johannes Kulick
2013-08-27 13:47 ` Austin Clements
2013-08-27 14:06 ` Johannes Kulick [this message]
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=20130827140654.31336.307@quirm.robotics.tu-berlin.de \
--to=johannes@mailless.org \
--cc=amdragon@MIT.EDU \
--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).