<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs, branch 0.20</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.20</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.20'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2015-04-03T00:29:05Z</updated>
<entry>
<title>emacs: show: hide large text attachments by default</title>
<updated>2015-04-03T00:29:05Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2015-03-28T11:08:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6518f0d2bc40957802904c6236b04510b9bfb9f6'/>
<id>urn:sha1:6518f0d2bc40957802904c6236b04510b9bfb9f6</id>
<content type='text'>
notmuch-show can be slow displaying large attachments so hide them by
default. The default maximum size is 10000 bytes/characters but it is
customizable.

Note that notmuch-show-insert-bodypart is also called from the reply
code so we need to be a little careful.
</content>
</entry>
<entry>
<title>emacs: Add a defcustom that specifies regexp for blocked remote images.</title>
<updated>2015-02-02T22:07:01Z</updated>
<author>
<name>Jinwoo Lee</name>
<email>jinwoo68@gmail.com</email>
</author>
<published>2015-02-02T21:04:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2049205e091a8c4dc89fb831dee7e9bb4fb06c15'/>
<id>urn:sha1:2049205e091a8c4dc89fb831dee7e9bb4fb06c15</id>
<content type='text'>
It's default value is ".", meaning all remote images will be blocked
by default.
</content>
</entry>
<entry>
<title>emacs: Support cid: references with shr renderer</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:17:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b74ed1cfad09f578e7c05ca5676d9d3d8c512a5e'/>
<id>urn:sha1:b74ed1cfad09f578e7c05ca5676d9d3d8c512a5e</id>
<content type='text'>
shr has really nice support for inline image rendering, but previously
we only had the hooks for w3m cid: references.
</content>
</entry>
<entry>
<title>emacs: Rewrite content ID handling</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:17:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f84cbb1d4d65b097507381491d953272a50fe2f8'/>
<id>urn:sha1:f84cbb1d4d65b097507381491d953272a50fe2f8</id>
<content type='text'>
Besides generally cleaning up the code and separating the general
content ID handling from the w3m-specific code, this fixes several
problems.

Foremost is that, previously, the code roughly assumed that referenced
parts would be in the same multipart/related as the reference.
According to RFC 2392, nothing could be further from the truth:
content IDs are supposed to be globally unique and globally
addressable.  This is nonsense, but this patch at least fixes things
so content IDs can be anywhere in the same message.

As a side-effect of the above, this handles multipart/alternate
content-IDs more in line with RFC 2046 section 5.1.2 (not that I've
ever seen this in the wild).  This also properly URL-decodes cid:
URLs, as per RFC 2392 (the previous code did not), and applies crypto
settings from the show buffer (the previous code used the global
crypto settings).
</content>
</entry>
<entry>
<title>emacs: Use generalized content caching in w3m CID code</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:17:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b0b5ced82b0a8cca2bbbe7b8b8c887c68b5afff0'/>
<id>urn:sha1:b0b5ced82b0a8cca2bbbe7b8b8c887c68b5afff0</id>
<content type='text'>
Previously this did its own caching, but this is now supported by more
generally by `notmuch-get-bodypart-binary'.
</content>
</entry>
<entry>
<title>emacs: Support caching in notmuch-get-bodypart-{binary,text}</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:17:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3687418526b155668578c1d70ccd6d9b63de2200'/>
<id>urn:sha1:3687418526b155668578c1d70ccd6d9b63de2200</id>
<content type='text'>
(The actual code change here is small, but requires re-indenting
existing code.)
</content>
</entry>
<entry>
<title>emacs: Return unibyte strings for binary part data</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:16:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9d19f325f5a0879e2f646e83e59595d5cb345de3'/>
<id>urn:sha1:9d19f325f5a0879e2f646e83e59595d5cb345de3</id>
<content type='text'>
Unibyte strings are meant for representing binary data.  In practice,
using unibyte versus multibyte strings affects *almost* nothing.  It
does happen to matter if we use the binary data in an image descriptor
(which is, helpfully, not documented anywhere and getting it wrong
results in opaque errors like "Not a PNG image: &lt;giant binary spew
that is, in fact, a PNG image&gt;").
</content>
</entry>
<entry>
<title>emacs: Remove broken `notmuch-get-bodypart-content' API</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:16:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=991efcded840944b2f7ebf97d4c9df51a3d011cf'/>
<id>urn:sha1:991efcded840944b2f7ebf97d4c9df51a3d011cf</id>
<content type='text'>
`notmuch-get-bodypart-content' could do two very different things,
depending on conditions: for text/* parts other than text/html, it
would return the part content as a multibyte Lisp string *after*
charset conversion, while for other parts (including text/html), it
would return binary part content without charset conversion.

This commit completes the split of `notmuch-get-bodypart-content' into
two different and explicit APIs: `notmuch-get-bodypart-binary' and
`notmuch-get-bodypart-text'.  It updates all callers to use one or the
other depending on what's appropriate.
</content>
</entry>
<entry>
<title>emacs: Create an API for fetching parts as undecoded binary</title>
<updated>2015-01-25T17:39:13Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:16:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=021906d6ec60360b5587ae08657fd6caa9a71b17'/>
<id>urn:sha1:021906d6ec60360b5587ae08657fd6caa9a71b17</id>
<content type='text'>
The new function, `notmuch-get-bodypart-binary', replaces
`notmuch-get-bodypart-internal'.  Whereas the old function was really
meant for internal use in `notmuch-get-bodypart-content', it was used
in a few other places.  Since the difference between
`notmuch-get-bodypart-content' and `notmuch-get-bodypart-internal' was
unclear, these other uses were always confusing and potentially
inconsistent.  The new call clearly requests the part as undecoded
binary.

This is step 1 of 2 in separating `notmuch-get-bodypart-content' into
two APIs for retrieving either undecoded binary or decoded text.
</content>
</entry>
<entry>
<title>emacs: Track full message and part descriptor in w3m CID store</title>
<updated>2015-01-25T17:39:12Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@mit.edu</email>
</author>
<published>2015-01-24T21:16:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c67a04de60d4f2f9060e41204f2fd50f1edc6a5c'/>
<id>urn:sha1:c67a04de60d4f2f9060e41204f2fd50f1edc6a5c</id>
<content type='text'>
This will simplify later changes.
</content>
</entry>
</feed>
