- *notmuch_messages_t* structure). Do note that the underlying
- library only provides a one-time iterator (it cannot reset the
- iterator to the start). Thus iterating over the function will
- "exhaust" the list of messages, and a subsequent iteration attempt
- will raise a :exc:`NotmuchError` STATUS.NOT_INITIALIZED. Also
- note, that any function that uses iteration will also
- exhaust the messages. So both::
-
- for msg in msgs: print msg
-
- as well as::
-
- number_of_msgs = len(msgs)
-
- will "exhaust" the Messages. If you need to re-iterate over a list of
- messages you will need to retrieve a new :class:`Messages` object.
-
- Things are not as bad as it seems though, you can store and reuse
- the single Message objects as often as you want as long as you
- keep the parent Messages object around. (Recall that due to
- hierarchical memory allocation, all derived Message objects will
- be invalid when we delete the parent Messages() object, even if it
- was already "exhausted".) So this works::
+ *notmuch_messages_t* structure). Do note that the underlying library
+ only provides a one-time iterator (it cannot reset the iterator to
+ the start). Thus iterating over the function will "exhaust" the list
+ of messages, and a subsequent iteration attempt will raise a
+ :exc:`NotmuchError` STATUS.NOT_INITIALIZED. Also note, that any
+ function that uses iteration will also exhaust the messages.If you
+ need to re-iterate over a list of messages you will need to retrieve
+ a new :class:`Messages` object or cache your :class:`Message`s in a
+ list via::
+
+ msglist = list(msgs)
+
+ You can store and reuse the single Message objects as often as you
+ want as long as you keep the parent Messages object around. (Recall
+ that due to hierarchical memory allocation, all derived Message
+ objects will be invalid when we delete the parent Messages() object,
+ even if it was already "exhausted".) So this works::