<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/emacs, branch 0.39</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.39</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.39'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2025-03-14T11:51:02Z</updated>
<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>
<entry>
<title>notmuch-show-imenu-prev-index-position-function: Don't recenter</title>
<updated>2025-02-18T12:54:36Z</updated>
<author>
<name>Damien Cassou</name>
<email>damien@cassou.me</email>
</author>
<published>2025-02-16T21:22:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0e10ca3a625c25c0238ecca2767aab7035b88a22'/>
<id>urn:sha1:0e10ca3a625c25c0238ecca2767aab7035b88a22</id>
<content type='text'>
The previous version of
notmuch-show-imenu-prev-index-position-function was calling
notmuch-show-previous-message which was recentering the window. This
is a problem when which-func-mode is active because which-func-mode is
called each time the user moves point around.

Because this function is only meant to be executed by imenu, there is
no reason to recenter the window. For the same reason, the new
implementation doesn't have to follow strictly how
notmuch-show-previous-message is implemented because imenu only places
point at very specific locations before calling
notmuch-show-imenu-prev-index-position-function.
</content>
</entry>
<entry>
<title>emacs/mua: Correct autoload cookies</title>
<updated>2024-08-16T20:39:20Z</updated>
<author>
<name>Pengji Zhang</name>
<email>me@pengjiz.com</email>
</author>
<published>2024-08-16T08:25:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2355ff274d3694fc79c655bb45c61245fb9a9302'/>
<id>urn:sha1:2355ff274d3694fc79c655bb45c61245fb9a9302</id>
<content type='text'>
This is a follow-up to [1: 8d06dfce]. Per Info node '(elisp)Autoload',
autoload cookies should start with ';;;###'.

1: 2024-04-04 8d06dfce175593aebae9a759c9167df4988a3444
   emacs: Autoload notmuch-user-agent related functions
</content>
</entry>
<entry>
<title>Revert "emacs: Fix saved-search buffer titles"</title>
<updated>2024-08-09T13:18:54Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-08-09T13:18:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e85abda157eac8888809b2dde885f60f312a5fb'/>
<id>urn:sha1:4e85abda157eac8888809b2dde885f60f312a5fb</id>
<content type='text'>
This reverts commit bc989209171d406b3671024542e59b86b0ecb23d.

This was applied unintentionally to master while still under discussion.
</content>
</entry>
<entry>
<title>emacs/tree: sanitize subjects when drawing tree</title>
<updated>2024-08-06T11:29:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2024-05-20T11:58:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bf9b9fe0469d24d1f0924074ffd5904363cb49cc'/>
<id>urn:sha1:bf9b9fe0469d24d1f0924074ffd5904363cb49cc</id>
<content type='text'>
This fixes the bug reported in

     id:6F2EF901-8B4B-44FF-83C5-22F732BA95A6@gmail.com

Unfortunately it turns out our test data has several tabs in the
subject lines. The expected output was updated to reflect their
removal and the ripple effect of several more subjects matching the
previous ones.
</content>
</entry>
</feed>
