<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs, branch 0.40</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.40</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.40'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2026-01-14T22:56:22Z</updated>
<entry>
<title>emacs/hello: fix one case of passing hide-excluded</title>
<updated>2026-01-14T22:56:22Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2025-06-15T20:12:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=97a2bad36a35399681f6c5f5a2b4390e6429d5ae'/>
<id>urn:sha1:97a2bad36a35399681f6c5f5a2b4390e6429d5ae</id>
<content type='text'>
In the search box (and recent searches), notmuch-search-hide-excluded
was not being passed to notmuch-search. This means that excluded
messages were always shown in the results. Fix this by passing the
extra argument.
</content>
</entry>
<entry>
<title>emacs: Generate and install autoloads</title>
<updated>2026-01-13T22:52:08Z</updated>
<author>
<name>Pengji Zhang</name>
<email>me@pengjiz.com</email>
</author>
<published>2024-08-18T07:42:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0469bcd1baf94548a4157effced6fee3a2f23cc6'/>
<id>urn:sha1:0469bcd1baf94548a4157effced6fee3a2f23cc6</id>
<content type='text'>
Previously when installed with 'make install', autoloads in sources
were not scraped. So users still had to load the full library
beforehand in order to use Notmuch.

Now we generate and install such a file for 'make install-emacs'. With
this change, users can replace in their Emacs configuration:

    (require 'notmuch)

with a much cheaper:

    (require 'notmuch-autoloads)

but are still able to use 'M-x notmuch'.

Note that this new file is not included in the 'make elpa' package, so
it does not break for those users, who have already been enjoying
autoloads generated by 'package.el'.

Besides, this should not break packaging for most distros. Even if
they have generated and maintained such a file using their package
managers, Emacs does not choke on an existing output file when
scraping autoloads.

Re: thread starting at id:87o75yl4u5.fsf@pengjiz.com

Amended-By: db; add comment about autoload-excludes
</content>
</entry>
<entry>
<title>emacs/search: call notmuch-search-mode before popping to buffer</title>
<updated>2025-06-20T15:57:18Z</updated>
<author>
<name>jonah</name>
<email>tschugg@posteo.de</email>
</author>
<published>2025-06-01T15:41:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=63665f1ebd6eff7753b7798add657fd6dbd110d6'/>
<id>urn:sha1:63665f1ebd6eff7753b7798add657fd6dbd110d6</id>
<content type='text'>
This makes derived-mode matching in display-buffer-alist work.
</content>
</entry>
<entry>
<title>emacs: fix disabling notmuch-show-header-line via custom</title>
<updated>2025-03-20T10:08:42Z</updated>
<author>
<name>len@realtimegenomics.com</name>
<email>len@realtimegenomics.com</email>
</author>
<published>2025-03-18T05:23:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d5ab2f0c02da4415e8775847ebc01559c9652e4c'/>
<id>urn:sha1:d5ab2f0c02da4415e8775847ebc01559c9652e4c</id>
<content type='text'>
The defcustom had a typo that prevented it from working as intended.
</content>
</entry>
<entry>
<title>Set 'untrusted-content' to t in all modes</title>
<updated>2025-03-14T11:51:02Z</updated>
<author>
<name>Stefan Kangas</name>
<email>stefankangas@gmail.com</email>
</author>
<published>2025-03-12T09:36:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=df4c1b5be769effb2ef7bc85c8bb8e09fb8f43fc'/>
<id>urn:sha1:df4c1b5be769effb2ef7bc85c8bb8e09fb8f43fc</id>
<content type='text'>
Instead of trying to guess in which modes this is safe not to set in,
let's just set it in all of them.

Background (added by db):

untrusted-content was added in Emacs 29.3 and is currently set by Gnus
and used by org-mode to prevent certain unsafe operations. I think the
intent is to use it for blocking more unsafe operations in the future.
</content>
</entry>
<entry>
<title>emacs/tree: add call to notmuch-hl-line-mode from process-filter</title>
<updated>2025-03-13T10:56:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-10T17:36:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d4e36a2df66868b921c49d1545f9f096b64459e1'/>
<id>urn:sha1:d4e36a2df66868b921c49d1545f9f096b64459e1</id>
<content type='text'>
This removes the visual gap/stutter between when the screen fills and
when the hl-line "cursor" is drawn.  It is not obviously how to
robustly test this, since it the observable effect is purely a matter
of timing.
</content>
</entry>
<entry>
<title>emacs/tree: call notmuch-hl-line-mode from tree-sentinel</title>
<updated>2025-03-13T10:56:05Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-10T17:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=41d5e5956e4a01fda4bfe07a2897939b04606c51'/>
<id>urn:sha1:41d5e5956e4a01fda4bfe07a2897939b04606c51</id>
<content type='text'>
There is a a perceptible gap between when the tree shows up and when
the hl-line is visible, but this is better than the previous state
where the line did not show up at all until the user moved the cursor.
</content>
</entry>
<entry>
<title>emacs/tree: condition hl-line-mode on notmuch-hl-line</title>
<updated>2025-03-13T10:55:21Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-10T17:36:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=43e90e7caa9cbb10097ed9526052fe82cd30b9f0'/>
<id>urn:sha1:43e90e7caa9cbb10097ed9526052fe82cd30b9f0</id>
<content type='text'>
It isn't clear that this call to hl-line-mode will survive the coming
re-organization to stop relying on hooks, but incrementally this at
least makes the disabling behaviour consistent.
</content>
</entry>
<entry>
<title>emacs: replace use of hook to draw hl-line in search mode</title>
<updated>2025-03-13T10:48:53Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-10T17:36:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5cb06b1893091cb069da990556e822c21a684acf'/>
<id>urn:sha1:5cb06b1893091cb069da990556e822c21a684acf</id>
<content type='text'>
In the thread at id:87fsfuuxwn.fsf@thinkbox, a bug is discussed where
the point and hl-line overlay get out of sync, leading the user to
open the wrong message. As far as I can tell this is caused by
notmuch-hl-mode being invoked too early.

This change bypasses the logic preventing notmuch-search-hook being
called only once, so that the overlay is updated later after the
buffer is full(er).

This change may lead to the overlay being updated multiple times; if
this is annoying we can add a similar buffer local variable to ensure
it is only called once.

The extra logic to check notmuch-search-target-line reduces the
flicker somewhat by not highlighting the first line every time.
</content>
</entry>
<entry>
<title>emacs: add defcustom to control hl-line mode</title>
<updated>2025-03-13T10:18:07Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-10T17:36:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b5ba3ff5ef9c2f39326883eff745108537aef89c'/>
<id>urn:sha1:b5ba3ff5ef9c2f39326883eff745108537aef89c</id>
<content type='text'>
Currently the presence of hl-line highlighting is controlled
implicitely by hooks. In future commits it will be migrated to use
this variable.
</content>
</entry>
</feed>
