mirror of
https://git.notmuchmail.org/git/notmuch
synced 2025-04-24 16:20:46 +02:00
notmuch clon
Such as reiserfs or xfs. This has been broken since the merge of support for rename and deletion of files from the mail store. Here's the original justification for the patch: A review of notmuch-new.c shows three uses of ->d_type: Near line 153, in _entries_resemble_maildir() we can simply allow for DT_UNKNOWN. This would fail if people have MH-style folders which have three folders called "new" "cur" and "tmp", but that seems unlikely, in which case the "tmp" folder would simply not be scanned. Near line 273 in add_files_recursive() we have another check. If DT_UNKNOWN, we fall through, then add_files_recursive() does a stat almost immediately, returning with success if the path isn't a directory. Thus, the fallback is already written. Finally, near line 343, in add_files_recursive() (a long function) we have another check. Here we can simply treat DT_UNKNOWN as DT_LNK, since the logic for the stat() results are the same. |
||
---|---|---|
compat | ||
config | ||
contrib | ||
lib | ||
packaging/fedora | ||
vim | ||
.gitignore | ||
AUTHORS | ||
configure | ||
COPYING | ||
COPYING-GPL-3 | ||
debugger.c | ||
gmime-filter-reply.c | ||
gmime-filter-reply.h | ||
INSTALL | ||
Makefile | ||
Makefile.local | ||
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 | ||
notmuch.el | ||
query-string.c | ||
README | ||
show-message.c | ||
TODO |
Notmuch - thread-based email index, search and tagging. Notmuch is a system for indexing, searching, reading, and tagging large collections of email messages. It uses the Xapian library to provide fast, full-text search of very large collection of email with a very 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.