thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.11 2012-01-05T21:48:46Z 2012-01-05T21:48:46Z Jameson Graef Rollins jrollins@finestructure.net 2012-01-02T22:23:02Z urn:sha1:74bced62b44b3b88431a0aec1194a74852446aed The name was originally notmuch-indent-messages-width, which is inconsistent with our variable naming convention. 2011-12-24T19:34:07Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-12-23T20:40:34Z urn:sha1:c44a0edadca995ddee4b159e9c465d40a32af6e4 Examples in documentation for `notmuch-search-line-faces' had an extra quote, e.g.: '(\"unread\" . '(:foreground \"green\")) Which resulted in values like: (\"unread\" quote (:foreground \"green\")) And tons of "Invalid face reference: quote" errors in the messages buffer. 2011-12-24T19:32:01Z Jameson Graef Rollins jrollins@finestructure.net 2011-12-23T04:59:12Z urn:sha1:c0d694035d128c1d80881878c269cd09f05794a5 Since message-ids necessarily match just a single message, there's no reason to do a search for the id before viewing the actual message; the search just becomes an extra screen to click through. Clicking on an id: links now just jumps straight to the message itself. 2011-12-23T12:29:04Z Aaron Ecay aaronecay@gmail.com 2011-12-22T14:24:20Z urn:sha1:8392a7cc54c4c08c0abbf2cc2707774f504ec33f Text properties change between characters; prev-s-c-property-change returns the position after the change. Thus, it is still inside the invisible region. 2011-12-22T11:41:02Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-12-22T00:23:50Z urn:sha1:49af79cd2a3be66e482039f1ef05cf909144230e Notmuch-hello stores a list of recent searches. Before the change, if a search from this list is repeated, the recent search list is not changed. The patch makes repeated recent searches move to the head of the list. I.e. the last search is always on top of the recent search list, which is what one would expect from a history list. 2011-12-22T10:56:41Z Thomas Jost schnouki@schnouki.net 2011-12-21T13:44:19Z urn:sha1:7edf9e2765d2795ca85dd2c239af20a7493e2085 This had been discussed and decided on IRC. Rationale: Therefore the space is recommended in the SI/ISO 31-0 standard, and the International Bureau of Weights and Measures states that "for numbers with many digits the digits may be divided into groups of three by a thin space, in order to facilitate reading. Neither dots nor commas are inserted in the spaces between groups of three". (http://en.wikipedia.org/wiki/Decimal_separator#Digit_grouping) 2011-12-22T10:56:26Z Thomas Jost schnouki@schnouki.net 2011-12-21T13:44:18Z urn:sha1:6dd482a16dd16252f9c5783ee65ce8bcd3d87eca In 123,456.78, "." is the decimal separator, but "," is the thousands separator. 2011-12-22T10:54:56Z David Edmondson dme@dme.org 2011-12-21T12:35:27Z urn:sha1:0fc424a1f00f49599c231e8dcbdb2fe156f237e3 If the address matching function generates no matches, don't prompt the user to choose between them (!). Instead, generate a message to report that there were no matches. 2011-12-22T10:54:29Z Jani Nikula jani@nikula.org 2011-12-20T19:53:14Z urn:sha1:d4c598dc9ed3af0d38fde9b9f0dcf6fa8dd62351 The :options keyword is not meaningful for function type. Also, it was not possible to enter nil value, contrary to the notmuch-mua-user-agent defcustom documentation. Specify the alternatives using choice type, taking nil into account. Signed-off-by: Jani Nikula <jani@nikula.org> 2011-12-22T10:54:10Z Jani Nikula jani@nikula.org 2011-12-20T19:53:13Z urn:sha1:2f7f259d6282bc9f91f4d46067a5313aba039f7f It was not possible to define custom filters or filter functions because the types were const. Remove const to allow editing. Signed-off-by: Jani Nikula <jani@nikula.org>