notmuch/bindings/ruby, branch feature/wildcardthread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=feature%2Fwildcard2025-03-08T14:42:19ZMerge 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:d81a173f73796de099c18cc26c37e24a807339e5ruby: use proper talloc flags2025-03-01T13:37:15ZFelipe Contrerasfelipe.contreras@gmail.com2025-01-02T01:39:35Zurn:sha1:e78e093330dff7cf85b2cf69314ea47c3dfb1080
This way talloc doesn't need to be installed in /usr.
ruby: simplify build2025-03-01T13:33:09ZFelipe Contrerasfelipe.contreras@gmail.com2025-01-02T01:39:34Zurn:sha1:5f9fc7d81a95c380e933189c05558cbecfcfdb99
We can just always add EXTRA_INCFLAGS and EXTRA_LDFLAGS.
ruby: db: reorganize initializer2023-05-29T10:51:02ZFelipe Contrerasfelipe.contreras@gmail.com2023-03-31T20:40:50Zurn:sha1:95a4bf38173311597bcc4fa7f597d58bb11ed119
In order to make it more extensible.
No functional changes.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
ruby: query: fix get sort2023-05-25T10:02:59ZFelipe Contrerasfelipe.contreras@gmail.com2023-04-03T20:27:21Zurn:sha1:afa45bd6b886838b760884a1870f274fc33b5f89
The order was wrong, right now `query.sort` doesn't return a number.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
ruby: remove FileNames object2023-04-12T10:30:01ZFelipe Contrerasfelipe.contreras@gmail.com2023-03-27T21:59:42Zurn:sha1:e4d75fcc8349ae95ec22d0e6679880d23bed37f8
Not used anymore now that we return an array of strings directly.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
ruby: filenames: return string array directly2023-04-12T10:29:48ZFelipe Contrerasfelipe.contreras@gmail.com2023-03-27T21:59:41Zurn:sha1:837426d7be63cf11d51b74464f174724935c5d4f
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
ruby: add filenames helper2023-04-12T10:05:23ZFelipe Contrerasfelipe.contreras@gmail.com2023-03-27T21:59:40Zurn:sha1:777b02a7d7b922bcae08af1c16e475051ec7d8f3
Right now it doesn't do much, but it will help for further
reorganization.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>