thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fstretch 2016-11-17T01:42:34Z 2016-11-17T01:42:34Z Mark Walters markwalters1009@gmail.com 2016-11-15T19:48:45Z urn:sha1:a3e712fa86a1f6df02a8be9f620f33ed9189069d Some of the recent changes to the emacs code have used functions introduced in emacs 24. The functions used are read-char-choice and setq-local. This changeset adds a file notmuch-compat.el which contains compatibility functions so that it should work on emacs 23. Note, since these functions are taken almost unchanged from the emacs source they are copyright the Free Software Foundation, and the header in the file reflects that. 2016-09-04T11:22:30Z Mark Walters markwalters1009@gmail.com 2016-09-03T22:59:38Z urn:sha1:74b54fb0faff4a6f69f1cf54dba9ac39e9aa754c This function prints diagnostic information in the event of an error. However, one of the callers has an optional :stdin-string keyword argument. This causes the error printing routine to error itself. Rather than reach notmuch-check-exit-status about the possible keyword arguments (currently only one but could be more in the future) this commit just tells notmuch-check-exit-status how to print non-string arguments. 2016-06-05T11:32:17Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2016-06-02T16:26:14Z urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb Many of the external links found in the notmuch source can be resolved using https instead of http. This changeset addresses as many as i could find, without touching the e-mail corpus or expected outputs found in tests. 2016-05-01T11:04:07Z David Edmondson dme@dme.org 2016-04-30T06:51:47Z urn:sha1:fdce7eb54532a0bdbd56ca3d56099b190eb7284c `notmuch--get-bodypart-raw' previously assumed that all non-binary MIME parts could be successfully read by assuming that they were UTF-8 encoded. This was demonstrated to be wrong, specifically when a part was marked as ISO8859-1 and included accented characters (which were incorrectly rendered as a result). Rather than assuming UTF-8, attempt to use the part's declared charset when reading it, falling back to US-ASCII if the declared charset is unknown, unsupported or invalid. 2016-04-16T11:24:42Z Chunyang Xu xuchunyang.me@gmail.com 2016-04-13T07:58:47Z urn:sha1:0cf457b73b4b666314d1a09ac3e31bd0fa2346a6 Refer to (info "(elisp) Library Headers") for package conventions. 2016-04-09T19:17:20Z David Edmondson dme@dme.org 2016-04-03T16:04:38Z urn:sha1:f0881394bd8bec4af8ddedf0a128648a3a4e2127 Currently the preference for which sub-part of a multipart/alternative part is shown is global. Allow to the user to override the settings on a per-message basis by providing the ability to call a function that has access to the message to return the discouraged type list. The original approach is retained as the default. 2016-03-27T20:44:24Z David Edmondson dme@dme.org 2016-03-08T17:12:59Z urn:sha1:c41d0db077f295c92b01b69ed001afa233b7d0f0 `notmuch-get-bodypart-text' assumed that it is always possible to acquire text/* parts via the sexp output format. This is not true if the part in question has a content type of application/octet-stream but is being interpreted as text/* based on the extension of the part filename. Rework `notmuch-get-bodypart-text' to use the raw output format to address this and make the implementation common with that of `notmuch-get-bodypart-binary'. 2015-11-23T12:40:40Z David Bremner david@tethera.net 2015-11-23T12:40:40Z urn:sha1:bceb6516cee170d3ad4b620826d48e90f05a12b1 Merge bugfixes applied directly to release 2015-11-23T12:37:19Z Mark Walters markwalters1009@gmail.com 2015-10-28T18:28:39Z urn:sha1:4c7a592d49266d588e717c232bc7aacbe4e16bfb Previously poll called from emacs would fail silently. This makes it return a useful error message. In the non-deprecated case of notmuch new and appropriate hooks, it uses notmuch-call-notmuch-process which gives an error and additionally puts the stdout/stderr etc in the *Notmuch errors* buffer. In the deprecated case of a custom poll script it only returns an error message. Commit based on a bug report, and a potential fix, by Ketil Malde. 2015-10-27T11:01:05Z Michal Sojka sojkam1@fel.cvut.cz 2015-10-26T23:22:48Z urn:sha1:89f78d38c1f7c9416e5bd9521dd694bb4f90572f Currently, notmuch has an address completion mechanism that requires external command to provide completion candidates. This commit adds a completion mechanism inspired by https://github.com/tjim/nevermore, which is implemented in Emacs lisp only. The preexisting address completion mechanism, activated by pressing TAB on To/Cc lines, is extended to use the new mechanism when notmuch-address-command to 'internal, which is the new default. The core of the new mechanism is the function notmuch-address-harvest, which collects the completion candidates from the notmuch database and stores them in notmuch-address-completions variable. The address harvesting can run either synchronously (same as with the previous mechanism) or asynchronously. When the user presses TAB for the first time, synchronous harvesting limited to user entered text is performed. If the entered text is reasonably long, this operation is relatively fast. Then, asynchronous harvesting over the full database is triggered. This operation may take long time (minutes on rotating disk). After it finishes, no harvesting is normally performed again and subsequent completion requests use the harvested data cached in memory. Completion cache is updated after 24 hours. Note that this commit restores (different) completion functionality for users when the user used external command named "notmuch-addresses", i.e. the old default. The result will be that the user will use the new mechanism instead of this command. I believe that many users may not even recognize this because the new mechanism works the same as http://commonmeasure.org/~jkr/git/notmuch_addresses.git and perhaps also as other commands suggested at http://notmuchmail.org/emacstips/#address_completion. [This feature was significantly improved by David Bremner and Mark Walters]