aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* show: Move format_part_content_raw with the other new-style formatsGravatar Austin Clements2012-03-18
| | | | Just code motion.
* show: Convert mbox format to new self-recursive styleGravatar Austin Clements2012-03-18
| | | | Given the lack of recursion, this is pretty easy.
* show: Move format_message_mbox with the other new-style formatsGravatar Austin Clements2012-03-18
| | | | Just code motion.
* show: Allow formatters to return errorsGravatar Austin Clements2012-03-18
| | | | | | | Formatter errors are propagated to the exit status of notmuch show. This isn't used by the JSON or text formatters, but it will be useful for the raw format, which is pickier.
* test: Fix malformed multipart messageGravatar Austin Clements2012-03-18
| | | | | | | | | | | | | | | | | | | | | | | Previously, there was only one CRLF between the terminating boundary of the embedded multipart/alternative and the boundary of the containing multipart. However, according the RFC 1341, 7.2.1: The boundary must be followed immediately either by another CRLF and the header fields for the next part, or by two CRLFs, in which case there are no header fields for the next part and The CRLF preceding the encapsulation line is considered part of the boundary so that it is possible to have a part that does not end with a CRLF (line break). Thus, there must be *two* CRLFs between these boundaries: one that ends the terminating boundary and one that begins the enclosing boundary. While GMime accepted the message we had before, it could not produce such a message.
* test: Fix typo in test descriptionGravatar Austin Clements2012-03-18
| | | | Part 4 is a multipart, not an html part.
* Merge tag '0.12_rc2'Gravatar David Bremner2012-03-18
|\ | | | | | | notmuch 0.12~rc2 release
| * debian: changelog stanza for 0.12~rc2Gravatar David Bremner2012-03-18
| | | | | | | | mention the two bugfixes
| * bump version to 0.12~rc2Gravatar David Bremner2012-03-18
| |
| * python: fix signature of two wrapped libnotmuch functionsGravatar Justus Winter2012-03-18
| | | | | | | | Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
| * Fix error reporting in notmuch_database_find_message_by_filenameGravatar Justus Winter2012-03-18
| | | | | | | | | | | | | | | | | | Formerly it was possible for *message_ret to be left uninitialized. The documentation however clearly states that "[o]n any failure or when the message is not found, this function initializes '*message' to NULL". Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
* | Merge branch 'release'Gravatar David Bremner2012-03-14
|\|
| * NEWS: emacs: enable `notmuch-search-line-faces' by defaultGravatar Jani Nikula2012-03-14
| |
* | Merge branch 'release'Gravatar David Bremner2012-03-14
|\|
| * NEWS: cli: manual page for notmuch configuration optionsGravatar Jani Nikula2012-03-14
| |
| * NEWS: emacs: inline patch fake attachment file namesGravatar Jani Nikula2012-03-14
| |
| * NEWS: emacs: support text/calendar MIME typeGravatar Jani Nikula2012-03-14
| |
| * NEWS: emacs: show view archiving key binding changesGravatar Jani Nikula2012-03-14
| |
| * NEWS: emacs: Fix MML tag quoting in repliesGravatar Jani Nikula2012-03-14
| |
* | Merge branch 'release'Gravatar David Bremner2012-03-13
|\|
| * debian: bump gmime dependency to 2.6.7Gravatar David Bremner2012-03-13
| | | | | | | | As explained in f34613e, if using gmime 2.6, we want at least 2.6.7
| * man: update SEE ALSO references in man pagesGravatar Jani Nikula2012-03-13
| | | | | | | | | | Drop references to notmuch-part(1). Reference all man pages. Fix man page section of notmuch-dump(1).
| * build: Require gmime >= 2.6.7Gravatar Thomas Jost2012-03-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gmime-2.6 had a bug [1] which made it impossible to tell why a signature verification failed when the signer key was unavailable (empty "sigstatus" field in the JSON output). Since 00b5623d the corresponding test is marked as broken when using gmime-2.6 (2.4 is fine). This bug has been fixed in gmime 2.6.5, which is now the minimal gmime-2.6 version required for building notmuch (gmime-2.4 is still available). As a consequence the version check in test/crypto can be removed. [Added by db] Although less unambigously a bug, Gmime 2.6 prior to 2.6.7 also was more strict about parsing, and rejected messages with initial "From " headers. This restriction is relaxed in [2]. For reasons explained in [3], we want to keep this more relaxed parsing for now. [1] https://bugzilla.gnome.org/show_bug.cgi?id=668085 [2] http://git.gnome.org/browse/gmime/commit/?id=d311f576baf750476e06e9a1367a2dc1793ea7eb [3] id:"1331385931-1610-1-git-send-email-david@tethera.net"
* | Merge branch 'release'Gravatar David Bremner2012-03-10
|\|
| * Fix configure script to properly detect gmime-2.6 if available.Gravatar Jameson Graef Rollins2012-03-10
| | | | | | | | | | | | | | Previously, the configure script would appear to detect gmime-2.6 if present. However, the binaries would end up being compiled against gmime-2.4. The addition of a break fixes things so that now gmime-2.6 will be used if available, falling back to gmime-2.4.
| * Handle errors in mime_node_openGravatar Austin Clements2012-03-10
| |
| * emacs: fix MML quoting in repliesGravatar Jani Nikula2012-03-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reply MML quoting added in commit ae438cc unintentionally MML quotes also the signature/encryption MML tags added via message-setup-hook, causing the reply not to be signed/encrypted. MML quote just the original message in the temp buffer before inserting it to the message buffer, to not interfere with message mode hooks or message construction in general. See [1] and [2] for bug reports. Thanks to Tim Bielawa <tbielawa@redhat.com> for testing. [1] id:"87hay78x6l.fsf@wyzanski.jamesvasile.com" [2] id:"1330812262-28272-1-git-send-email-tbielawa@redhat.com". Signed-off-by: Jani Nikula <jani@nikula.org>
* | emacs-hello: Do not calculate the count of the messages in hidden sectionsGravatar Michal Sojka2012-03-10
| | | | | | | | | | The result is that hello screen shows much faster when some sections are hidden.
* | Make exclusion visible againGravatar David Bremner2012-03-03
| | | | | | | | | | | | | | | | This reverts dfee0f9 man: remove search.exclude_tags from notmuch-config.1 for 0.12 e83409d NEWS: revert NEWS item for exclude tags for 0.12 e77b031 config: disable addition of exclude tags for 0.12
* | Merge branch 'release'Gravatar David Bremner2012-03-03
|\|
| * Actually close the xapian database in notmuch_database_closeGravatar Justus Winter2012-03-03
| | | | | | | | | | | | | | | | | | | | | | Formerly the xapian database object was deleted and closed in its destructor once the object was garbage collected. Explicitly call close() so that the database and the associated lock is released immediately. The comment is a courtesy of Austin Clements. Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>
| * debian: Bump standards versionGravatar David Bremner2012-03-03
| | | | | | | | No actual changes are needed.
| * debian: update .gitignoreGravatar David Bremner2012-03-03
| | | | | | | | Ignore individual binary package directories.
| * debian: add notmuch_query_add_tag_exclude to exported symbolsGravatar David Bremner2012-03-03
| | | | | | | | | | This symbol is added in 0.12, although we are "stealthing" the feature overall.
| * man: remove search.exclude_tags from notmuch-config.1 for 0.12Gravatar Mark Walters2012-03-03
| |
| * NEWS: revert NEWS item for exclude tags for 0.12Gravatar Mark Walters2012-03-02
| |
| * config: disable addition of exclude tags for 0.12Gravatar Mark Walters2012-03-02
| | | | | | | | | | This disables the addition of search_exclude_tags in notmuch-setup and notmuch-config.
* | emacs: notmuch.el ignore excluded matchesGravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | | | This is a small change to make notmuch.el ignore excluded matches. In the future it could do something better like add a button for rerunning the search with the excludes (particularly if nothing matches with the excludes) or having them invisible and allowing the visibility to be toggled.
* | emacs: show: recognize the exclude flag.Gravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | Show mode will recognize the exclude flag by not opening excluding messages by default, and will start at the first matching non-excluded message. If there are no matching non-excluded messages it will go to the first matching (necessarily excluded) message.
* | cli: omit excluded messages in results where appropriate.Gravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | | | | | | | | | | | | | In all cases of notmuch count/search/show where the results returned cannot reflect the exclude flag return just the matched not-excluded results. If the caller wishes to have all the matched results (i.e., including the excluded ones) they should call with the --no-exclude option. The relevant cases are count: both threads and messages search: all cases except the summary view show: mbox format
* | man: update manpage for notmuch-show --no-exclude optionGravatar Mark Walters2012-03-02
| |
* | test: update tests to reflect the exclude flagGravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | notmuch show outputs the exclude flag so many tests using notmuch show failed. This commit adds "excluded:0" or "excluded: false" to the expected outputs. After this commit there should be no failing tests.
* | cli: Make notmuch-show respect excludes.Gravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | | | This adds the excludes to notmuch-show.c. We do not exclude when only a single message (or part) is requested. notmuch-show will output the exclude information when either text or json format is requested. As this changes the output from notmuch-show it breaks many tests (in a trivial and expected fashion).
* | test: update search test to reflect exclude flagGravatar Mark Walters2012-03-02
| | | | | | | | | | | | notmuch-search.c now returns all matching threads even if it the match is a search.tag_excluded message (but with a mark indicating this). Update the test to reflect this.
* | lib: Add the exclude flag to notmuch_query_search_threadsGravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | | | | | | | | | Add the NOTMUCH_MESSAGE_FLAG_EXCLUDED flag to notmuch_query_search_threads. Implemented by inspecting the tags directly in _notmuch_thread_create/_thread_add_message rather than as a Xapian query for speed reasons. Note notmuch_thread_get_matched_messages now returns the number of non-excluded matching messages. This API is not totally desirable but fixing it means breaking binary compatibility so we delay that.
* | lib: Make notmuch_query_search_messages set the exclude flagGravatar Mark Walters2012-03-02
| | | | | | | | | | | | | | | | | | | | Add a flag NOTMUCH_MESSAGE_FLAG_EXCLUDED which is set by notmuch_query_search_messages for excluded messages. Also add an option omit_excluded_messages to the search that we do not want the excludes at all. This exclude flag will be added to notmuch_query_search threads in the next patch.
* | lib: Rearrange the exclude code in query.ccGravatar Mark Walters2012-03-02
| | | | | | | | | | Slightly refactor the exclude code to give the callers access to the exclude query itself. There should be no functional change.
* | test: add tests for new cli --no-exclude optionGravatar Mark Walters2012-03-02
| | | | | | | | | | | | The tests test the new --no-exclude option to search and count. There were no existing tests for the exclude behaviour for count so added these too.
* | cli: Add --no-exclude to the man pages for search and countGravatar Mark Walters2012-03-02
| |
* | cli: add --no-exclude option to count and search.Gravatar Mark Walters2012-03-02
| | | | | | | | | | | | This option turns off the exclusion so all matching messages are returned. We do not need to add this to notmuch-show as that does not (yet) exclude.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-09 23:58:30 +0000