~vcs-imports/notmuch/trunk : changes

~vcs-imports/notmuch/trunk » Changes from revision 2360

From Revision 2360 to 2341

Rev	Summary	Authors	Date
2360	NEWS: start section for 0.13 NEWS: start section for 0.13 People are making patches for the 0.12 NEWS section for features that won't be there. Let's help them out by adding a new stanza.	David Bremner	12 years ago
2359	emacs: Fix search tab completion in terminals emacs: Fix search tab completion in terminals In X, Emacs distinguishes the tab key, which produces a 'tab event; from C-i, which produces a ?\t event. However, in a terminal, these are indistinguishable and only produce a ?\t event. In order to simplify things, Emacs automatically translates from 'tab to ?\t (see "Function key translations" in M-x describe-bindings), so functions only need to be bound to ?\t to work in all situations. Previously, the search tab completion code usedq (kbd "<tab>"), which produced the event sequence [tab], which only matched the 'tab event and hence only worked in X. This patch changes it to (kbd "TAB"), which matches the general ?\t event and works in all situations.	Austin Clements	12 years ago
2358	lib: fix an exclude bug lib: fix an exclude bug When the exclude tags contain a tag that does not occur anywhere in the Xapian database the exclusion fails. We modify the way the query is constructed to `work around' this. (In fact the new code is cleaner anyway.) It also seems to fix another exclusion failure bug reported by jrollins but we have not yet worked out why it helps in that case.	Mark Walters	12 years ago
2357	test: add tests for message only search test: add tests for message only search This adds three tests for --output=messages searches. One test is for the case when one exclude tag does not occur in the Xapian database. This triggers a Xapian bug in some cases and causes the whole exclusion to fail. The next commit avoids this bug.	Mark Walters	12 years ago
2356	test: the test for the exclude code mistakenly excludes the ... test: the test for the exclude code mistakenly excludes the tag "=" The tests for the exclude code in search and count use the line notmuch config set search.exclude_tags = deleted which actually sets the exclude tags to be "=" and "deleted". Remove the "=" from this line.	Mark Walters	12 years ago
2355	lib: Add exclude query debug output lib: Add exclude query debug output	Austin Clements	12 years ago
2354	lib: Expose query debug output via an environment variable lib: Expose query debug output via an environment variable Allow query debugging to be enabled at run-time by setting the NOTMUCH_DEBUG_QUERY environment variable to a non-empty string. Previously, enabling query debugging required recompiling, but parsed queries are often useful for tracking down bugs in situations where recompiling is inconvenient.	Austin Clements	12 years ago
2353	cli: Parsing. Allow true/false parameter for boolean options... cli: Parsing. Allow true/false parameter for boolean options. Allow NOTMUCH_OPT_BOOLEAN to take a true or false parameter. In particular it allows the user to turn off a boolean option with --option=false.	Mark Walters	12 years ago
2352	test: use subtest name for generated message subject by defa... test: use subtest name for generated message subject by default Before the change, messages generated by generate_message() used "Test message #N" for default subject where N is the generated messages counter. Since message subject is commonly present in expected results, there is a chance of breaking other tests when a new generate_message() call is added. The patch changes default subject value for generated messages to subtest name if it is available. If subtest name is not available (i.e. message is generated during test initialization), the old default value is used (in this case it is fine to have the counter in the subject). Another benefit of this change is a sane default value for subject in generated messages, which would allow to simplify code like: test_begin_subtest "test for a cool feature" add_message [subject]="message for test for a cool feature"	Dmitry Kurochkin	12 years ago
2351	test: remove "Generate some messages" test from raw test: remove "Generate some messages" test from raw Before the change, the first subtest in raw format tests just generated messages and checked that they are added successfully. This is not really a raw format test, it is creating of environment required for other subtests to run. The patch removes the first subtest from raw and replaces it with bare add_message calls, similar to how it is done in other tests. TODO: we should check that test environment was created successfully. Currently, many tests do add_message(), notmuch new and other calls without checking the results. We should come up with a general solution for this, i.e. if any command during test initialization fails, all tests should be skipped with appropriate error message.	Dmitry Kurochkin	12 years ago
2350	man: Update raw format documentation man: Update raw format documentation	Austin Clements	12 years ago
2349	show: Convert raw format to the new self-recursive style, pr... show: Convert raw format to the new self-recursive style, properly support interior parts This is fully compatible for root and leaf parts, but now has proper support for interior parts. This requires some design decisions that were guided by what I would want if I were to save a part. Specifically: - Leaf parts are printed without headers and with transfer decoding. This is what makes sense for saving attachments. (Furthermore, the transfer decoding is necessary since, without the headers, the caller would not be able to interpret non-transfer-decoded output.) - Message parts are printed with their message headers, but without enclosing part headers. This is what makes sense for saving a message as a whole (which is a message part) and for saving attached messages. This is symmetric for whole messages and for attached messages, though we special-case the whole message for performance reasons (and corner-case correctness reasons: given malformed input, GMime may not be able to reproduce it from the parsed representation). - Multipart parts are printed with their headers and all child parts. It's not clear what the best thing to do for multipart is, but this was the most natural to implement and can be justified because such parts can't be interpreted without their headers. As an added benefit, we can move the special-case code for part 0 into the raw formatter.	Austin Clements	12 years ago
2348	show: Move format_part_content_raw with the other new-style ... show: Move format_part_content_raw with the other new-style formats Just code motion.	Austin Clements	12 years ago
2347	show: Convert mbox format to new self-recursive style show: Convert mbox format to new self-recursive style Given the lack of recursion, this is pretty easy.	Austin Clements	12 years ago
2346	show: Move format_message_mbox with the other new-style form... show: Move format_message_mbox with the other new-style formats Just code motion.	Austin Clements	12 years ago
2345	show: Allow formatters to return errors show: Allow formatters to return errors 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.	Austin Clements	12 years ago
2344	test: Fix malformed multipart message test: Fix malformed multipart message 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.	Austin Clements	12 years ago
2343	test: Fix typo in test description test: Fix typo in test description Part 4 is a multipart, not an html part.	Austin Clements	12 years ago
2342	Merge tag '0.12_rc2' Merge tag '0.12_rc2' notmuch 0.12~rc2 release	David Bremner	12 years ago
2341	Merge branch 'release' Merge branch 'release'	David Bremner	12 years ago

Older »