thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.5 2010-11-11T11:40:19Z 2010-11-11T11:40:19Z Carl Worth cworth@cworth.org 2010-11-11T11:36:13Z urn:sha1:8480a0a00370f997a29ebf98560a799ece43d3f4 The notmuch_filenames_t object might easily outlive the original object owning the filename list. So take a talloc reference to keep things safe. 2010-11-11T11:40:19Z Carl Worth cworth@cworth.org 2010-11-11T08:07:24Z urn:sha1:1d02dd64afe245a2b5a8461feeba975e61f0c233 This augments the existing notmuch_message_get_filename by allowing the caller access to all filenames in the case of multiple files for a single message. To support this, we split the iterator (notmuch_filenames_t) away from the list storage (notmuch_filename_list_t) where previously these were a single object (notmuch_filenames_t). Then, whenever the user asks for a file or filename, the message object lazily creates a complete notmuch_filename_list_t and then: For notmuch_message_get_filename, returns the first filename in the list. For notmuch_message_get_filenames, creates and returns a new iterator for the filename list. 2010-11-11T11:40:19Z Carl Worth cworth@cworth.org 2010-11-11T07:26:31Z urn:sha1:d87db8843266caf6b11c1f2f1874328830b23878 The new implementation is simply a talloc-based list of strings. The former support (a list of database terms with a common prefix) is implemented by simply pre-iterating over the terms and populating the list. This should provide no performance disadvantage as callers of thigns like notmuch_directory_get_child_files are very likely to always iterate over all filenames anyway. This new implementation of notmuch_filenames_t is in preparation for adding API to query all of the filenames for a single message.