notmuch/tag-util.h, branch 0.19 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.19 2014-03-06T11:41:38Z cli: export function for illegal tag checking 2014-03-06T11:41:38Z Jani Nikula jani@nikula.org 2014-02-23T16:55:21Z urn:sha1:07dd9d53cb7d92dc42ef697edb65e4c491b65928 This lets us check for forbidden tags consistently across the cli. No functional changes. tag-util: do not reset list in parse_tag_command_line 2013-06-29T17:36:23Z Peter Wang novalazy@gmail.com 2013-06-23T04:23:55Z urn:sha1:f00c925bd10c024d5b9f88d8903c7a0d14e9cc6a The 'insert' command will be better served if parse_tag_command_line modifies a pre-populated list (of new.tags) instead of clobbering the list outright. The sole existing caller, notmuch_tag_command, is unaffected by this change. notmuch-tag.c: convert to use tag-util 2013-01-08T00:42:21Z David Bremner bremner@debian.org 2012-12-25T19:42:39Z urn:sha1:e9b6e464745fdebd4c6367dfc731859fe390b531 Command line parsing is factored out into a function parse_tag_command_line in tag-util.c. There is some duplicated code eliminated in tag_query, and a bunch of translation from using the bare tag_op structs to using that tag-utils API. tag-utils: use the tag_opt_list_t as talloc context, if possible. 2012-12-23T03:13:15Z David Bremner bremner@debian.org 2012-12-16T19:58:15Z urn:sha1:ba4e8565294fc0a197b4c08082ad912c31888008 The memory usage discipline of tag_op_list_t is never to free the internal array of tag operations before freeing the whole list, so it makes sense to take advantage of hierarchical de-allocation by talloc. By not relying on the context passed into tag_parse_line, we can allow tag_op_list_t structures to live longer than that context. tag-util.[ch]: New files for common tagging routines 2012-12-09T17:33:34Z David Bremner bremner@debian.org 2012-11-13T01:54:16Z urn:sha1:fb50cc41fe6f508118697d65a44e8f742a466ca0 These are meant to be shared between notmuch-tag and notmuch-restore. The bulk of the routines implement a "tag operation list" abstract data type act as a structured representation of a set of tag operations (typically coming from a single tag command or line of input).