aboutsummaryrefslogtreecommitdiff
path: root/bindings/ruby/query.c
Commit message (Collapse)AuthorAge
* ruby: Add wrapper for notmuch_query_set_omit_excluded()Ali Polatel2012-05-08
|
* ruby: Add wrapper for notmuch_query_add_tag_excludeAli Polatel2012-05-08
|
* ruby: Add wrapper for notmuch_query_count_messagesAli Polatel2012-05-08
|
* ruby: be consistent with notmuch's coding styleAli Polatel2011-10-04
| | | | No functional change, just indentation
* ruby: Rename destroy to destroy!Ali Polatel2011-09-24
| | | | | | | | | | | | | | | | | According to the common Ruby function naming convention, potentially dangerous functions or functions which operate on the object itself are suffixed with an exclamation mark. Both of these are true for object destroying functions. The following modules are affected: - Notmuch::Directory - Notmuch::FileNames - Notmuch::Query - Notmuch::Threads - Notmuch::Thread - Notmuch::Messages - Notmuch::Message - Notmuch::Tags
* ruby: Add wrappers for query_get_s{ort,tring}Ali Polatel2011-01-25
| | | | | | New wrappers: notmuch_query_get_sort(): QUERY.sort notmuch_query_get_query_string(): QUERY.to_s
* ruby: Don't barf if an object is destroyed more than onceAli Polatel2010-06-06
| | | | | | Raise RuntimeError instead. Also revise Notmuch::Database a bit. Add Notmuch::Database.open singleton method.
* ruby: Kill garbage collection related cruft.Ali Polatel2010-06-06
| | | | | | | Let the user destroy objects that she wants explicitly. It's not possible to specify the order objects are garbage collected. See id:86y6f8v838.fsf@harikalardiyari.ev on ruby-talk for more information.
* Initial ruby bindingsAli Polatel2010-06-06
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-04 06:48:09 +0000