notmuch/bindings, branch feature/git-remotethread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=feature%2Fgit-remote2025-07-04T10:35:39Zpython/doc: fix link to notmuch-config manpage2025-07-04T10:35:39ZDavid Bremnerdavid@tethera.net2025-06-22T19:32:21Zurn:sha1:59d83bf958ef0b0c4811274ad928723b0f69112e
This docstring has been like this a long time, but recently I noticed
sphinx-doc complaining about :man:. This :any: link seems to work, and
is consistent with the other links to the notmuch-config man page.
bindings/python-cffi: fix typos2025-06-16T11:05:37ZJakub Wilkjwilk@jwilk.net2025-03-19T19:28:31Zurn:sha1:babacbd1b188004b388033cf20662eda51965365python: make IndexOptions public2025-03-29T15:32:09ZJakub Wilkjwilk@jwilk.net2025-03-24T07:55:42Zurn:sha1:d8ebc9cf80b6d10e72a01d7b0afa42aab6b31264
Database docstrings refer to IndexOptions,
so the latter should be public too.
Merge branch 'release'2025-03-18T12:15:32ZDavid Bremnerdavid@tethera.net2025-03-18T12:15:32Zurn:sha1:890fd10082a61bd109ee28c03eedac4294e2ae3cdoc/python: correct wording around container complexity.2025-03-18T12:15:16ZDavid Bremnerdavid@tethera.net2025-02-22T17:42:49Zurn:sha1:eaf3cd10db95b366c960a4f87e4a513dc9488e7f
Based on a suggestion from Jakub Wilk.
Merge branch 'release'2025-03-14T00:29:26ZDavid Bremnerdavid@tethera.net2025-03-14T00:29:26Zurn:sha1:2454feddd136781a963fa8990074a1bdaf3ce3dfbindings/python-cffi: fix docstring for message.header()2025-03-14T00:18:15ZMichael J Grubergit@grubix.eu2025-03-04T12:39:43Zurn:sha1:5802f5d6269172222a6fccf5908eae833014917b
The cffi bindings raise a LookupError in case a header is not present.
Adjust the docstring to say so.
The legacy bindings behaved differently, and this is one of the things
to be aware of when migrating to the cffi bindings.
Merge branch 'release'2025-03-08T14:42:19ZDavid Bremnerdavid@tethera.net2025-03-08T14:42:19Zurn:sha1:85b7a2f86aeadf937f06531986993fda98a13e89ruby: fix "undefining the allocator of T_DATA" warnings2025-03-08T14:39:22ZJohannes Larsenmail@johslarsen.net2024-09-01T00:02:10Zurn:sha1:e8261872dc65ea0259971ff44721a2f7d3f34e67
Ruby 3.2 introduced a warning when C-extensions use structs without
redefining the allocation default allocation routine meant for objects.
See https://bugs.ruby-lang.org/issues/18007 for details.
In the Ruby bindings this happens at `Data_Wrap_Notmuch_Object` call
sites, so the object types used there needed to update their allocation.
This ruby code (given a database at the hardcoded path with messages
matching `tag:tmp`) exercise all the ruby objects:
require 'notmuch'
Notmuch::Database.open File.expand_path("~/mail") do |db|
db.get_directory("/tmp")
db.query("tag:tmp").search_threads.each do |t|
t.messages.each do |m|
puts m.header("Subject")
end
end
end
Before these changes with ruby 3.2.5 and notmuch 0.38.3 it outputs:
notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Query
notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Threads
notmuch.rb:5: warning: undefining the allocator of T_DATA class Notmuch::Thread
notmuch.rb:6: warning: undefining the allocator of T_DATA class Notmuch::Messages
notmuch.rb:6: warning: undefining the allocator of T_DATA class Notmuch::Message
notmuch release 0.38.3 now available
(the last line is the message I tagged with tmp), and after the changes:
notmuch release 0.38.3 now available
ruby: trivial build cleanup2025-03-01T13:38:33ZFelipe Contrerasfelipe.contreras@gmail.com2025-01-02T01:39:36Zurn:sha1:d81a173f73796de099c18cc26c37e24a807339e5