<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs, branch 0.14</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.14</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.14'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-08-12T19:30:10Z</updated>
<entry>
<title>emacs: Make moving to the previous message move to the previous boundary</title>
<updated>2012-08-12T19:30:10Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-14T03:47:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c3119c45e1b93a9d5a3925e9ecad70c886ca5064'/>
<id>urn:sha1:c3119c45e1b93a9d5a3925e9ecad70c886ca5064</id>
<content type='text'>
Previously, notmuch-show-previous-message would move to the beginning
of the message before the message containing point.  This patch makes
it instead move to the previous message *boundary*.  That is, if point
isn't already at the beginning of the message, it moves to the
beginning of the current message.  This is consistent with
notmuch-show-next-message, which can be thought of as moving to the
next message boundary.  Several people have expressed a preference for
this.
</content>
</entry>
<entry>
<title>emacs: notmuch search bugfix</title>
<updated>2012-08-12T19:27:45Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-08-07T16:32:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5811550cdd51485ec7ea0f960139eb9ea1741451'/>
<id>urn:sha1:5811550cdd51485ec7ea0f960139eb9ea1741451</id>
<content type='text'>
The recent change to use json for notmuch-search.el introduced a bug
in the code for keeping position on refresh. The problem is a
comparison between (plist-get result :thread) and a thread-id returned
by notmuch-search-find-thread-id: the latter is prefixed with
"thread:"

We fix this by adding an option to notmuch-search-find-thread-id to
return the bare thread-id. It appears that notmuch-search-refresh-view
is the only caller of notmuch-search that supplies a thread-id so this
change should be safe (but could theoretically break users .emacs
functions).
</content>
</entry>
<entry>
<title>emacs: Fix "not defined at runtime" warning</title>
<updated>2012-08-12T19:05:08Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-08-08T21:40:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=07b5f97202c840d97bd9f53c62c4192a6b0adf30'/>
<id>urn:sha1:07b5f97202c840d97bd9f53c62c4192a6b0adf30</id>
<content type='text'>
Previously, the Emacs byte compiler produced the warning

    the function `remove-if-not' might not be defined at runtime.

because we only required cl at compile-time (not runtime).  This fixes
this warning by requiring cl at runtime, ensuring that the definition
of remove-if-not is available.
</content>
</entry>
<entry>
<title>emacs: show: exclude bug fix</title>
<updated>2012-08-03T00:13:19Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-07-28T11:56:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1efb6e7ae16ede7feccffc1864a206bec3caf337'/>
<id>urn:sha1:1efb6e7ae16ede7feccffc1864a206bec3caf337</id>
<content type='text'>
The pipe message function (when used with a prefix) uses a search of
the form "id:&lt;id1&gt; or id:&lt;id2&gt;" etc. Since the user says precisely
which messages are wanted by opening them it should not use excludes.
</content>
</entry>
<entry>
<title>emacs: fix a bug introduced by the recent search cleanups.</title>
<updated>2012-08-03T00:11:53Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2012-08-02T07:19:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3fa00020eaac7dfb403cac239a5e59fb2b5d3e2c'/>
<id>urn:sha1:3fa00020eaac7dfb403cac239a5e59fb2b5d3e2c</id>
<content type='text'>
In commit 5d0883e the function notmuch-search-next-thread was changed.
In particular it only goes to the next message if there is a next
message. This breaks notmuch-show-archive-thread-then-next. Fix this
by going to the "next" message whenever we are on a current message.
</content>
</entry>
<entry>
<title>emacs: Fix navigation of multi-line search result formats</title>
<updated>2012-07-24T12:23:53Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-21T17:37:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5d0883ea1bf5419589ba27c12994c36495f89255'/>
<id>urn:sha1:5d0883ea1bf5419589ba27c12994c36495f89255</id>
<content type='text'>
At this point, the only remaining functions that don't support
multi-line search result formats are the thread navigation functions.
This patch fixes that by rewriting them in terms of
notmuch-search-result-{beginning,end}.

This changes the behavior of notmuch-search-previous-thread slightly
so that if point isn't at the beginning of a result, it first moves
point to the beginning of the result.
</content>
</entry>
<entry>
<title>emacs: Allow custom tags formatting</title>
<updated>2012-07-24T12:23:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-21T17:37:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=90e741ef81668d9b7db62b57e9a0c88877e2631e'/>
<id>urn:sha1:90e741ef81668d9b7db62b57e9a0c88877e2631e</id>
<content type='text'>
Previously we ignored any notmuch-search-result-format customizations
for tag formatting because we needed to be able to parse back in the
result line and update the tags in place.  We no longer do either of
these things, so we can allow customization of this format.

(Coincidentally, previously we still allowed too much customization of
the tags format, since moving it earlier on the line or removing it
from the line would interfere with the tagging mechanism.  There is
now no problem with doing such things.)
</content>
</entry>
<entry>
<title>emacs: Replace other search text properties with result property</title>
<updated>2012-07-24T12:21:48Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-21T17:37:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e94b45112ec7262224fdaae03bae75eb47cdece0'/>
<id>urn:sha1:e94b45112ec7262224fdaae03bae75eb47cdece0</id>
<content type='text'>
Since the result object contains everything that the other text
properties recorded, we can remove the other text properties and
simply look in the plist of the appropriate result object.
</content>
</entry>
<entry>
<title>emacs: Use result text properties for search result iteration</title>
<updated>2012-07-24T12:21:38Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-21T17:37:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7ba5c86399f8c479442938dd2cc7ad07edd4d985'/>
<id>urn:sha1:7ba5c86399f8c479442938dd2cc7ad07edd4d985</id>
<content type='text'>
This simplifies the traversal of regions of results and eliminates the
need for save-excursions (which tend to get in the way of maintaining
point when we make changes to the buffer).  It also fixes some strange
corner cases in the old line-based code where results that bordered
the region but were not included in it could be affected by region
commands.  Coincidentally, this also essentially enables multi-line
search result formats; the only remaining non-multi-line-capable
functions are notmuch-search-{next,previous}-thread, which are only
used for interactive navigation.
</content>
</entry>
<entry>
<title>emacs: Update tags by rewriting the search result line in place</title>
<updated>2012-07-24T12:04:50Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-07-21T17:37:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2a91f636d8c3d478619c0a5040685aca1ac75842'/>
<id>urn:sha1:2a91f636d8c3d478619c0a5040685aca1ac75842</id>
<content type='text'>
Now that we keep the full thread result object, we can refresh a
result after any changes by simply deleting and reconstructing the
result line from scratch.

A convenient side-effect of this wholesale replacement is that search
now re-applies notmuch-search-line-faces when tags change.
</content>
</entry>
</feed>
