1 [[!img notmuch-logo.png alt="Notmuch logo" class="left"]]
2 #List of features people have requested and ideas that people want to keep thinking about
8 Removes unread and inbox tags, adds deleted tag.
10 When used from a search results view, it deletes the thread that
13 When used from the thread view, it deletes the currently
14 displayed message inside the thread.
18 Removes unread and inbox tags, adds deleted tag.
20 When used from a search results view, it deletes the thread that
21 the cursor is on (just like 'd')
23 When used from the thread view, it deletes the currently
24 displayed thread (and not just the message)
26 + Add '???' keybinding
28 Skips current thread without archiving it
30 Right now 'n' gets me to the end of a thread, but not to the
31 beginning of the next thread. 'a' gets you to the next thread,
32 but archives the current one.
34 + Allow different "real names" for the optional email addresses
36 if only one name is configured, use that for all addresses;
37 if other_names are configured, match those with the other_email addresses
39 + Put the the emacs mode in a separate repository and include it as a submmodule in main (better for emacs package managers among other things).
43 + Add hooks for retagging:
44 + pre-tag: Called before tagging messages
45 + post-tag: Called after messages got tagged
47 This might be useful if you want to sync for example your Maildirs with the notmuch tags.
49 + Allow a custom location for .notmuch
51 The notmuch index is currently saved in .notmuch under the user's
52 Maildir and there's no configuration option to change that.
54 This is problematic with both tools that sync Maildirs and with IMAP
55 servers that consider .notmuch a Maildir subfolder (e.g. dovecot)
57 A better solution would be to add a configuration option for this so
58 that it can be put e.g. in ~/.notmuch
60 + Add a list or pattern for subfolders to ignore
62 Some people are crazy enough to archive e.g. their Spam in their
63 Maildir and perhaps they'd prefer not having them indexed on notmuch.
65 Having a configuration option to exclude or include certain subparts of
66 the user's Maildir would be a very nice feature to have.
68 + Index more headers. Some desired headers:
70 + Received: allows for searches based on the arrival path
71 + Reply-To: allows for searches based on the return address
73 + Allow anchors in searches
75 `notmuch search from:domain.org$` only matches if "domain.org" is
76 at the end of the From: header
78 `notmuch search from:^username` only matches if "username" is at
79 the beginning of the From: header (right after the ':')
81 This leaves the interesting question if we want a way to bind to
82 the actual address component.
84 + Add folder tags to mail automatically
86 Add the name of the IMAP folder as the tag for mails. This way,
87 server-side filtering can be directly used by notmuch to tag all
90 + Make message store code modular
92 Notmuch is built on the assumption that the message store is a
93 collection of message files in directories (roughly Maildir
94 format). This performs suboptimally for a wide range of systems,
95 especially with large numbers of messages. Modularising the
96 message store code to move this assumption into the implementation
97 rather than the interface would allow adding support for different
98 message stores like the traditional [mbox
99 formats](http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/mail-mbox-formats.html)
100 as well as more experimental approaches like using git as an object
101 storage (similar to how [[nmbug]] operates).
103 + Put content of all non-multipart content-types in results of `notmuch show --format=json ...`
105 In the JSON-format output of the `show` command, only text/plain
106 parts' content is included. Including the content of parts having any
107 non-multipart content-type would assist with those who wished to access
108 their mail through notmuch's `show` command (because of having written
109 their MUA in a language with no library bindings or access to them
110 [e.g. Perl, Lua or shell]) and also had a mailcap or similar MIME-type
111 mapping system with which to actually view HTML files, images and the like.
117 NOTE: most of notmuchsync's functionality has been integrated in
118 notmuch 0.5. It probably doesn't make much sense to requests
119 features for it, rather than notmuch itself.
121 + DONE: id:"878w8niy83.fsf@SSpaeth.de"
122 Add feature to move files in the maildir hierarchy
124 `notmuchsync --move "searchstring" "targetfolder"`
126 Where searchstring is any valid notmuch search