similar to: ruby bindings documentation

Hello. I've improved the Xapian Ruby bindings by adding aliasing a few methods and making the code and examples more in line with Ruby conventions. I also wrote a simple script to generate a skeleton so that rdoc can automatically document some of the SWIG code to a limited extent. I used a template I find somewhat nicer than the default, but if you don't like it, it can easily be changed.

Bugs item #17013, was opened at 2008-01-11 06:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=17013&group_id=35 Category: Missing API call Group: None Status: Open Resolution: None Priority: 3 Submitted By: Daniel Brumbaugh Keeney (db-keen) Assigned to: Nobody (None) Summary: Notebook#get_current_page Initial Comment: Notebook#get_current_page

Carrying on this conversation: http://lists.tartarus.org/pipermail/xapian-discuss/2007-March/003513.html void TermGenerator::set_stopper(stopper) Stopper * stopper CODE: // FIXME: no corresponding SvREFCNT_dec(), but a leak seems better than // a SEGV! SvREFCNT_inc(ST(1)); THIS->set_stopper(stopper); It would be good to fix these FIXMEs. A class-level HASH could be

I'm posting this here to help others who might be having the same issue. I maintain xapian-core ruby gem. I was trying to upgrade to 1.4.2 and had some issues. The generated makefile doesn’t work because of the following: docs/rdocs/index.html: docs/xapian.rb rm -rf docs/rdocs $(MKDIR_P) docs cd docs && $(RDOC) --op rdocs `test -f xapian.rb||echo '$(abs_srcdir)/'`xapian.rb

On Sat, Dec 02, 2023 at 10:24:57PM +0300, Vitaly Chikunov wrote: > JFYI. I am not sure it's worth reporting but, when building 2.5.5 for ALT Talking of small inconsistencies, 2.5.5 isn't a Xapian version... > I noticed small inconsistencies in configure output. > > 1. xapian-binding: > > checking for /usr/bin/rdoc... no > checking for rdoc... /usr/bin/rdoc >

Hi, JFYI. I am not sure it's worth reporting but, when building 2.5.5 for ALT I noticed small inconsistencies in configure output. 1. xapian-binding: checking for /usr/bin/rdoc... no checking for rdoc... /usr/bin/rdoc Looks curious but no problem since it's found anyway. 2. xapian-core when built with GCC: checking whether __builtin_add_overflow is declared... yes ...

As discussed on IRC. The naming conventions aren't ideal, but the intent feels right and it works for me. J -- /--------------------------------------------------------------------------\ James Aylett xapian.org james at tartarus.org uncertaintydivision.org -------------- next part -------------- Index:

Oh, by the way, just running `make all` works fine too, which is what I am now doing in the gem.. but fixing the makefile would retain the existing working behaviour of `make clean all` which was fine in 1.2.x On 16 January 2017 at 14:21, Samuel Williams <space.ship.traveller at gmail.com> wrote: > I'm posting this here to help others who might be having the same issue. > > I

When I first got involved with Red Hat (back with 5.2 in the early 90's) I learned the hard way not to use language-specific packaging systems like CPAN for Perl because they'd conflict with RPM's database and make it much harder to manage what was installed on my system. If I now need a package for which no RPM is available, I'll use a utility like cpanspec to repackage it

Hi Olly and co, On an Ubuntu 15.10, following the docs at https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package When running debuild -e PHP_VERSIONS=5 -us -uc I get (sorry for the French): " dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: paquet source xapian-bindings dpkg-buildpackage: version source 1.2.21-2.1 dpkg-buildpackage: distribution source unstable

On Wed, May 24, 2023 at 02:18:50AM +0000, nebulaaksum wrote: > I have more question. After successfully installing xapian-bindings-1.4.22. I continued to install xapian-omega-1.4.22. But it did not even pass the configuration step. > I intend to install xapian-omega-1.4.22 at > /usr/local/xapian-omega-1.4.22. I do my building from a separate > build directory lest I clutter my

Dear xapian discussion, I was just installing xapian-bindings-1.4.22 on Ubuntu 22.04, but I got the following warning message: configure: WARNING: Xapian library is version 1.4.18 but the bindings are version 1.4.22 - we strongly recommend using matching versions. I tried to check my xapian core-1.4.22 for the library, but could not find that library. How do I fix this? I will appreciate your

Le 26/03/16 18:04, Olly Betts a ?crit : > On Sat, Mar 26, 2016 at 04:51:35PM -0500, Yannick Warnier wrote: >> On an Ubuntu 15.10, following the docs at >> https://trac.xapian.org/wiki/FAQ/PHP%20Bindings%20Package >> >> When >> >> running debuild -e PHP_VERSIONS=5 -us -uc >> >> I get (sorry for the French): >> >> >> "

On Mon, May 22, 2023 at 10:35:25PM +0000, nebulaaksum wrote: > I was just installing xapian-bindings-1.4.22 on Ubuntu 22.04, but I > got the following warning message: > > configure: WARNING: Xapian library is version 1.4.18 but the bindings > are version 1.4.22 - we strongly recommend using matching versions. The issue here is mostly that xapian-bindings wraps almost the entire

On Thu, Oct 21, 2004 at 05:45:42PM +0100, Olly Betts wrote: > Log message: > python/docs/bindings.html: Remove documentation explicitly saying > how we wrap Xapian::QueryParser and Xapian::Stem since we wrap them > exactly as we wrap everything else we don't mention! Also mention > simpleexpand example. The point of this comment was to highlight that they exist within the

On Tue, May 23, 2023 at 03:06:50AM +0000, nebulaaksum wrote: > You said, " Generally xapian-bindings with a newer xapian-core (within > the same stable release series) should work." > But it is the newer xapian-core-1.4.22 which is installed in my system > already that is having Xapian library version 1.4.18, So the > xapian-bindings-1.4.22 is saying the core an older

I discovered, while trying to set up Tcl bindings for Notmuch (https://notmuchmail.org/), which uses Xapian, that flintlock was not being locked (I had lost updates). I then found that opening a Xapian database for writing directly via the Xapian Tcl bindings also silently fails to lock flintlock. I have taken a copy of flint_lock.cc to play with, and I find that it locks the file when called

I can't quite connect the dots on this, perhaps someone can help. I'm simply trying to create an in-memory database comprising a single document, so that I can run a load of queries against it and see if any of them match the new document (this is to enable users to have 'subscriptions' to saved searches and be alerted every time a new item is published that matches their

Hi, I've just noticed that set_max_wildcard_expansion() has been removed in favour of set_max_expansion() in Xapian. Has the new method been added to the Perl-bindings? We have some old Perl code that uses set_max_wildcard_expansion(), and I have a test of too large expansion that now returns "something terrible happened" instead of"Exception: Wildcard ... expands too much

Very odd this, I have downloaded the latest xapian-core and bindings. Installed xapian-core no problem in /usr/local/xapian However I am getting very strange errors when running make when trying to install the PHP bindings, it configures fine. Paste bin here: http://pastebin.com/JWViJz4b I am missing something obvious I know... I have built 1.0 on this machine in the past fine... John