aboutsummaryrefslogtreecommitdiffhomepage
path: root/bindings/ruby/tags.c
Commit message (Collapse)AuthorAge
* ruby: be consistent with notmuch's coding styleGravatar Ali Polatel2011-10-04
| | | | No functional change, just indentation
* ruby: Rename destroy to destroy!Gravatar 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: Don't barf if an object is destroyed more than onceGravatar Ali Polatel2010-06-06
| | | | | | Raise RuntimeError instead. Also revise Notmuch::Database a bit. Add Notmuch::Database.open singleton method.
* ruby: Kill garbage collection related cruft.Gravatar 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 bindingsGravatar Ali Polatel2010-06-06