Update news & manpages to notmuch version 0.16

[obsolete/notmuch-wiki] / feature-requests.mdwn

diff --git a/feature-requests.mdwn b/feature-requests.mdwn
index 8083173988db2380b60467bbe73287d345e24fa5..cf8dc7b3b60b4388deb12ad0abe53266f40c7dae 100644 (file)
--- a/feature-requests.mdwn
+++ b/feature-requests.mdwn
@@ -1,5 +1,20 @@
 [[!img notmuch-logo.png alt="Notmuch logo" class="left"]]
-#List of features people have requested and ideas that people want to keep thinking about
+#  List of features people have requested and ideas that people want to keep thinking about
+
+*********************
+
+**WARNING**: This page is going away. It seems like nobody who works on
+  notmuch reads it regularly, and there is no convenient way to
+  discuss ideas with the people who propose them.  Please use
+  [notmuch mailing list](http://notmuchmail.org/mailman/listinfo/notmuch)
+  instead.
+
+*********************
+
+## TODO list
+
+See the [devel/TODO file](http://git.notmuchmail.org/git/notmuch/blob/HEAD:/devel/TODO) in the
+[notmuch git repository](http://git.notmuchmail.org/git/notmuch).
 
 ## Emacs client
 
@@ -36,9 +51,18 @@
      if only one name is configured, use that for all addresses;
      if other_names are configured, match those with the other_email addresses
 
-
++    Put the the emacs mode in a separate repository and include it as a
+     submodule in main (better for emacs package managers among other
+     things).
+        
 ## notmuch
 
++    Add hooks for retagging:
+   + pre-tag: Called before tagging messages
+   + post-tag: Called after messages got tagged
+
+     This might be useful if you want to sync for example your Maildirs with the notmuch tags.
+
 +    Allow a custom location for .notmuch
 
      The notmuch index is currently saved in .notmuch under the user's
@@ -93,6 +117,16 @@
      as well as more experimental approaches like using git as an object
      storage (similar to how [[nmbug]] operates).
 
++    Put content of all non-multipart content-types in results of `notmuch show --format=json ...`
+
+     In the JSON-format output of the `show` command, only text/plain
+     parts' content is included.  Including the content of parts having any
+     non-multipart content-type would assist with those who wished to access
+     their mail through notmuch's `show` command (because of having written
+     their MUA in a language with no library bindings or access to them
+     [e.g. Perl, Lua or shell]) and also had a mailcap or similar MIME-type
+     mapping system with which to actually view HTML files, images and the like.
+
 ## 3rd party apps
 
 ### notmuchsync