mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 02:48:08 +01:00
notmuch clon
26d8d960ee
When displaying threads as result of a search it makes sense to list those authors first who match the search. The matching authors are separated from the non-matching ones with a '|' instead of a ',' Imagine the default "+inbox" query. Those mails in the thread that match the query are actually "new" (whatever that means). And some people seem to think that it would be much better to see those author names first. For example, imagine a long and drawn out thread that once was started by me; you have long read the older part of the thread and removed the inbox tag. Whenever a new email comes in on this thread, prior to this patch the author column in the search display will first show "Dirk Hohndel" - I think it should first show the actual author(s) of the new mail(s). Signed-off-by: Dirk Hohndel <hohndel@infradead.org> |
||
---|---|---|
bindings/python | ||
compat | ||
completion | ||
debian | ||
emacs | ||
lib | ||
packaging | ||
test | ||
vim | ||
.gitignore | ||
AUTHORS | ||
configure | ||
COPYING | ||
COPYING-GPL-3 | ||
debugger.c | ||
gmime-filter-headers.c | ||
gmime-filter-headers.h | ||
gmime-filter-reply.c | ||
gmime-filter-reply.h | ||
INSTALL | ||
json.c | ||
Makefile | ||
Makefile.local | ||
NEWS | ||
notmuch-client.h | ||
notmuch-config.c | ||
notmuch-count.c | ||
notmuch-dump.c | ||
notmuch-new.c | ||
notmuch-reply.c | ||
notmuch-restore.c | ||
notmuch-search-tags.c | ||
notmuch-search.c | ||
notmuch-setup.c | ||
notmuch-show.c | ||
notmuch-tag.c | ||
notmuch-time.c | ||
notmuch.1 | ||
notmuch.c | ||
notmuch.desktop | ||
query-string.c | ||
README | ||
RELEASING | ||
show-message.c | ||
TODO | ||
version |
Notmuch - thread-based email index, search and tagging. Notmuch is a system for indexing, searching, reading, and tagging large collections of email messages in maildir or mh format. It uses the Xapian library to provide fast, full-text search with a convenient search syntax. Notmuch is free software, released under the GNU General Public License version 3 (or later). Building notmuch ---------------- See the INSTALL file for notes on compiling and installing notmuch. Contacting users and developers ------------------------------- The website for Notmuch is: http://notmuchmail.org The mailing list address for the notmuch community is: notmuch@notmuchmail.org We welcome any sort of questions, comments, kudos, or code there. Subscription is not required, (but if you do subscribe you'll avoid any delay due to moderation). See the website for subscription information. There is also an IRC channel dedicated to talk about using and developing notmuch: IRC server: irc.freenode.net Channel: #notmuch Interface options ----------------- Notmuch includes a "notmuch" command-line interface to the system. This is not a very convenient interface and it is not expected that users will find it satisfying. Instead, there are two option for obtaining a more sophisticated interface: 1. Build on top of the "notmuch" command-line interface. This might be a reasonable option for a very text-oriented client environment. For example, an emacs-based interface for notmuch is already under development and is available in the notmuch.el file in this distribution. If someone were to write a curses-based interface, or similar, it might also be reasonable to build on the "notmuch" command-line interface. 2. Build on top of the notmuch library interface. This is a better choice for developing an interface that has full control of the presentation of email threads and messages. It is expected that anyone integrating Notmuch into an existing, graphical email program use the notmuch library interface. The public interface to the notmuch library is contained in the notmuch.h header file. The "notmuch" command-line program in notmuch.c can be used as good example code, since it is a simple program that is written on top of the library interface. As can be seen, alternate interfaces to the Notmuch mail system are still in development. We would appreciate any contributions to these efforts.