| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | cli: config: make notmuch_config_open() "is new" parameter input only |  Jani Nikula | 2013-03-07 |
| | | | | | | | | | We now have a notmuch_config_is_new() function to query whether a config was created or not. Change the notmuch_config_open() is_new parameter into boolean create_new to determine whether the function should create a new config if one doesn't exist. This reduces the complexity of the API. | ||
| * | dump: Disallow \n in message IDs |  Austin Clements | 2013-01-06 |
| | | | | | | | | | | | | | | | | When we switch to using regular Xapian queries in the dump format, \n will cause problems, so we disallow it. Specially, while Xapian can quote and parse queries containing \n without difficultly, quoted queries containing \n still span multiple lines, which breaks the line-orientedness of the dump format. Strictly speaking, we could still round-trip these, but it would significantly complicate restore as well as scripts that deal with tag dumps. This complexity would come at absolutely no benefit: because of the RFC 2822 unfolding rules, no amount of standards negligence can produce a message with a message ID containing a line break (not even Outlook can do it!). Hence, we simply disallow it. | ||
| * | test: add generator for random "stub" messages |  David Bremner | 2012-12-02 |
| Initial use case is testing dump and restore, so we only have message-ids and tags. The message ID's are nothing like RFC compliant, but it doesn't seem any harder to roundtrip random UTF-8 strings than RFC-compliant ones. Tags are UTF-8, even though notmuch is in principle more generous than that. updated for id:m2wr04ocro.fsf@guru.guru-group.fi - talk about Unicode value rather some specific encoding - call talloc_realloc less times | |||
 |
index : notmuch | |
| thread-based email index, search and tagging |
| aboutsummaryrefslogtreecommitdiffhomepage |