<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs, branch 0.23_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.23_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.23_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2016-09-25T10:42:01Z</updated>
<entry>
<title>emacs: tag deleted face bugfix</title>
<updated>2016-09-25T10:42:01Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-09-18T10:57:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=51d27e08555ac3187bd9d5649a0074ba6a9aabce'/>
<id>urn:sha1:51d27e08555ac3187bd9d5649a0074ba6a9aabce</id>
<content type='text'>
Commit d25d33ff cleaned up some of the tag face code. However, for the
face notmuch-tag-deleted it used the test

((class color) (supports :strike-through))

to decide whether to use red strikethrough or inverse-video (emacs in
a terminal typically doesn't support red strikethrough, but in X it does).

However, it seems that test often returns true even though red
strikethrough is not supported. This breaks the tag update code -- the
wrong thing is displayed to the user.

Thus we make the test explicitly more specific, changing the test to

((class color) (supports :strike-through "red"))
</content>
</entry>
<entry>
<title>emacs: tree: make jump close message pane</title>
<updated>2016-09-24T13:08:24Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-09-19T09:39:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7b2d7d65126b11ce08079b7cf235e1073fb1c22b'/>
<id>urn:sha1:7b2d7d65126b11ce08079b7cf235e1073fb1c22b</id>
<content type='text'>
j is in the global notmuch keymap bound to notmuch jump. In tree-mode
it makes sense to close the message pane first (otherwise the new
search runs in the small top pane of tree-mode).
</content>
</entry>
<entry>
<title>emacs: reply: remove wrong sig/enc status buttons</title>
<updated>2016-09-18T13:57:27Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-09-13T01:45:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a448879e49fb838a302b4e68d73e63c6b75d9175'/>
<id>urn:sha1:a448879e49fb838a302b4e68d73e63c6b75d9175</id>
<content type='text'>
This stops the (usually incorrect) sigstatus and encstatus buttons
appearing when replying in emacs, and updates the test suite to match.

Overriding the status button functions is a little unusual but much
less intrusive than passing an argument all the way down the call
chain. It also makes it clear exactly what it does.

We also hide the application/pgp-encrypted part as it can only contain
"Version: 1". We do this in notmuch show, which means it also happens
when replying.
</content>
</entry>
<entry>
<title>emacs: make the remaining faces configurable.</title>
<updated>2016-09-12T11:12:10Z</updated>
<author>
<name>Matt Armstrong</name>
<email>marmstrong@google.com</email>
</author>
<published>2016-08-14T22:17:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d25d33ff2d818d5a423e07b7f465add9c970dc75'/>
<id>urn:sha1:d25d33ff2d818d5a423e07b7f465add9c970dc75</id>
<content type='text'>
I believe this moves all "anonymous" face specifications in notmuch
code into a configurable defface.
</content>
</entry>
<entry>
<title>emacs: implement notmuch-search-color-line with dolist.</title>
<updated>2016-09-12T11:08:45Z</updated>
<author>
<name>Matt Armstrong</name>
<email>marmstrong@google.com</email>
</author>
<published>2016-08-14T22:13:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3856286e21ab4ef282bbb262b700477282327923'/>
<id>urn:sha1:3856286e21ab4ef282bbb262b700477282327923</id>
<content type='text'>
While passing a lambda to mapc is idiomatic elisp, dolist is easier
to understand, and there are a few other calls to it in this file.
</content>
</entry>
<entry>
<title>emacs: wash: make word-wrap bound message width</title>
<updated>2016-09-12T11:06:00Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-08-06T15:29:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7b7960ea228ca0449e2711377dfdebc23a791147'/>
<id>urn:sha1:7b7960ea228ca0449e2711377dfdebc23a791147</id>
<content type='text'>
Previously if notmuch-wash-wrap-lines-length was set then all messages
would be wrapped at this value (or window-width if that is
smaller). This was done regardless of the message's depth in a thread --
for example, if the n.w.w.l.l is 80 and the messages depth is 20
(so indented 20 by default) the messages text only got 60 characters
of space.

This commit changes that so a message always gets the full n.w.w.l.l
of width regardless of its indentation (unless that goes over
window-width of course).
</content>
</entry>
<entry>
<title>emacs: show: let the user override the mime-type of an attachment</title>
<updated>2016-09-12T11:03:34Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-07-11T07:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f94921520778ae4005500f5d1b943e2d4ddd3b2a'/>
<id>urn:sha1:f94921520778ae4005500f5d1b943e2d4ddd3b2a</id>
<content type='text'>
This allows the user to override the mime-type of a part in the show
buffer. This takes the simple option of displaying the part with the
specified mime-type in its own buffer (in view mode). This avoids
further complicating the part handling code.

Bound to ". m" (i.e., m in the part map). Then the user can either
enter a mime-type (with completion to all mime types that mailcap (and
thus notmuch) knows about, or press return for the default choice of
text/plain.
</content>
</entry>
<entry>
<title>emacs: use define-derived-mode for defining modes.</title>
<updated>2016-09-10T16:07:54Z</updated>
<author>
<name>Steven Allen</name>
<email>steven@stebalien.com</email>
</author>
<published>2016-08-28T18:41:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e954310d70674a439a50cf4c699467567095b057'/>
<id>urn:sha1:e954310d70674a439a50cf4c699467567095b057</id>
<content type='text'>
This sets up and runs all the correct hooks and reduces some redundancy.
</content>
</entry>
<entry>
<title>emacs: maildir: add the actual insert code</title>
<updated>2016-09-04T11:23:14Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-09-03T22:59:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fce8146a8b738f2317034fee6236cdbd3597849b'/>
<id>urn:sha1:fce8146a8b738f2317034fee6236cdbd3597849b</id>
<content type='text'>
With all the preparation it is now simple to add the actual insert
code. Since insert can fail for many reasons we let the user decide
interactively deal with it.

We modify test-lib.el to set file fcc, so that all the old tests and
emacs_fcc_message from test-lib.sh still work
</content>
</entry>
<entry>
<title>Modify our local copy of message-do-fcc</title>
<updated>2016-09-04T11:23:04Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2016-09-03T22:59:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cf59859b2028223cdf1741a2a09eadb666ccb726'/>
<id>urn:sha1:cf59859b2028223cdf1741a2a09eadb666ccb726</id>
<content type='text'>
Since we also need to use this code for the draft handling we split
message-do-fcc into convenient sub-chunks (functions or macros as
appropriate).
</content>
</entry>
</feed>
