<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs/notmuch.el, branch 0.5</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.5</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.5'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-11-12T01:28:48Z</updated>
<entry>
<title>emacs: add stash thread-id function to notmuch-search mode</title>
<updated>2010-11-12T01:28:48Z</updated>
<author>
<name>Jameson Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2010-09-18T19:48:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2b433736a56ec1ccac67ada9cc81337a157a45a2'/>
<id>urn:sha1:2b433736a56ec1ccac67ada9cc81337a157a45a2</id>
<content type='text'>
This add a "stash-map" for search-mode, just like in show-mode, and
adds one function, bound to "i" to stash the thread-id of the current
selected thread.

Couldn't think of the correct way to stash other thread info, so I
didn't add any other stash functions for now.
</content>
</entry>
<entry>
<title>Don't use kill-this-buffer to kill notmuch emacs buffers</title>
<updated>2010-11-08T17:02:54Z</updated>
<author>
<name>Jameson Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2010-11-06T20:49:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7171e77d4d1e83fdf9c7a56987b98bce3f181598'/>
<id>urn:sha1:7171e77d4d1e83fdf9c7a56987b98bce3f181598</id>
<content type='text'>
kill-this-buffer appears to be a function intended specifically for
use in the menu bar, and causes problem killing notmuch buffers when
multiple frames have been used.  This patch replaces kill-this-buffer
with notmuch-kill-this-buffer, which in turn just simply calls
(kill-buffer (current-buffer)).
</content>
</entry>
<entry>
<title>emacs: Re-work the implementation of highlighting in notmuch-search-mode.</title>
<updated>2010-10-29T22:30:43Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2010-06-07T14:35:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f99ad42da03afd638bfdfdea92d1cbdd3b510b8f'/>
<id>urn:sha1:f99ad42da03afd638bfdfdea92d1cbdd3b510b8f</id>
<content type='text'>
Re-write `notmuch-search-color-line', with the following improvements:
 - create overlays only if they will be needed,
 - merge the properties specified for a tag on top of any matching a
   previous tag.
</content>
</entry>
<entry>
<title>emacs: Fix the autoload comments</title>
<updated>2010-10-29T22:27:01Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-29T22:27:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b11ecf613a3e574ff80e0e9ec5825b43b541ab12'/>
<id>urn:sha1:b11ecf613a3e574ff80e0e9ec5825b43b541ab12</id>
<content type='text'>
Remove them from non-top-level entry points, (such as the functions to
set notmuch modes and the deprecated notmuch-folder function). And add
one to the notmuch-hello function. Also, add missing documentation
string to notmuch-hello.
</content>
</entry>
<entry>
<title>Don't involve the shell in notmuch searches</title>
<updated>2010-10-29T21:13:51Z</updated>
<author>
<name>David Benjamin</name>
<email>davidben@MIT.EDU</email>
</author>
<published>2010-06-04T00:29:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=adbfff40caeef27b912dbeb2bf3d1038a6e6cab0'/>
<id>urn:sha1:adbfff40caeef27b912dbeb2bf3d1038a6e6cab0</id>
<content type='text'>
The shell isn't needed to interpret any of the arguments, so don't
bother using it at all.

Signed-off-by: David Benjamin &lt;davidben@mit.edu&gt;
</content>
</entry>
<entry>
<title>emacs: Eliminate warning of calling function with excess arguments.</title>
<updated>2010-10-28T01:04:38Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-28T01:04:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c9e0da3a1aaa640da330fe82fa906bb84463736b'/>
<id>urn:sha1:c9e0da3a1aaa640da330fe82fa906bb84463736b</id>
<content type='text'>
Yet another case of "how could this have possibly worked before?!".

I guess we were just getting very lucky with the emacs lisp calling
conventions and what happens with extra arguments, but, ick! Much
better now.
</content>
</entry>
<entry>
<title>emacs: Remove non-interactive call of goto-line</title>
<updated>2010-10-28T00:58:19Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-28T00:58:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=75f703e7c2fe33920342c1bc534d19935c1e3513'/>
<id>urn:sha1:75f703e7c2fe33920342c1bc534d19935c1e3513</id>
<content type='text'>
As the emacs compiler warns, the goto-line function is only intended for
interactive use. Instead use the approach recommended in the goto-line
documentation to avoid this.
</content>
</entry>
<entry>
<title>emacs: Avoid runtime use of `cl'.</title>
<updated>2010-10-28T00:41:50Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2010-04-29T10:33:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c506e1034b5adb54b3e4f8d3e59086756f2bb126'/>
<id>urn:sha1:c506e1034b5adb54b3e4f8d3e59086756f2bb126</id>
<content type='text'>
The GNU Emacs Lisp Reference Manual section D.1 says:

&gt; *  Please don't require the cl package of Common Lisp extensions at
&gt;    run time. Use of this package is optional, and it is not part of
&gt;    the standard Emacs namespace. If your package loads cl at run time,
&gt;    that could cause name clashes for users who don't use that package.
&gt;
&gt;    However, there is no problem with using the cl package at compile
&gt;    time, with (eval-when-compile (require 'cl)). That's sufficient for
&gt;    using the macros in the cl package, because the compiler expands
&gt;    them before generating the byte-code.

Follow this advice, requiring the following changes where `cl' was
used at runtime:

- replace `rassoc-if' in `notmuch-search-buffer-title' with the `loop'
  macro and inline code. At the same time find the longest prefix
  which matches the query rather than simply the last,
- replace `union', `intersection' and `set-difference' in
  `notmuch-show-add-tag' and `notmuch-show-remove-tag' with local code
  to calculate the result of adding and removing a list of tags from
  another list of tags.
</content>
</entry>
<entry>
<title>emacs: Fix bug when parsing a subject cotaining: \[[0-9/]\]</title>
<updated>2010-09-23T20:21:03Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-09-23T20:21:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=31a5e5a12595c4130d3a7b95b53567003de0b2c9'/>
<id>urn:sha1:31a5e5a12595c4130d3a7b95b53567003de0b2c9</id>
<content type='text'>
That is, a subject with a bracketed set of digits (and optionally a
slash), for example "[2010]" would cause the emacs code to misparse
the search results. Fix this by tweaking the regular expression.
</content>
</entry>
<entry>
<title>emacs: In search mode, truncate authors using invisible text.</title>
<updated>2010-06-04T02:12:23Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2010-05-19T07:03:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=17b09af22809d32cd6bf8050bb30f80d9810944f'/>
<id>urn:sha1:17b09af22809d32cd6bf8050bb30f80d9810944f</id>
<content type='text'>
Rather than discarding authors when truncated to fit the defined
column width, mark the text beyond the end of the column as invisible
and allow `isearch' to be used over the text so hidden.

This allows us to retain the compact display whilst enabling a user to
find the elided text.
</content>
</entry>
</feed>
