search for: lemony

.../glib/gquark.h:30, from /usr/include/glib-2.0/glib/gerror.h:24, from /usr/include/glib-2.0/glib/gunicode.h:25, from accentnormalisingitor.h:22, from /u1/olly/xapian-svn-snapshot/tags/0.9.4/xapian/xapian-core/queryparser/queryparser.lemony:24: /usr/include/glib-2.0/glib/gtypes.h:30:24: glibconfig.h: No such file or directory In file included from /usr/include/glib-2.0/glib/gquark.h:30, from /usr/include/glib-2.0/glib/gerror.h:24, from /usr/include/glib-2.0/glib/gunicode.h:25, from ac...

Hi All, I wanted to add a small tweak to my installation of the Query Parser. Should I be editing queryparser.lemony? I tried that and the make didn't include my change. I applied the same change to queryparser_internal.cc and it worked fine. Is the .lemony file something used internally and I can ignore? Or do I need to run something prior to make to convert the files? Thanks, Mike Boone. http://boonedocks....

...-2.0/glib/gquark.h:30, from /usr/include/glib-2.0/glib/gerror.h:24, from /usr/include/glib-2.0/glib/gunicode.h:25, from accentnormalisingitor.h:22, from /u1/olly/xapian-svn-snapshot/trunk/xapian/xapian-core/queryparser/queryparser.lemony:24: /usr/include/glib-2.0/glib/gtypes.h:30:24: glibconfig.h: No such file or directory In file included from /usr/include/glib-2.0/glib/gquark.h:30, from /usr/include/glib-2.0/glib/gerror.h:24, from /usr/include/glib-2.0/glib/gunicode.h:25, from a...

...y $query = $qp->parse_query($query_string, Search::Xapian::FLAG_DEFAULT); [...] Here's a gdb backtrace for a crash: Program received signal SIGSEGV, Segmentation fault. ~TermGroup (yypParser=0x2b58170, yymajor=<value optimized out>, yypminor=0x386a7f8) at queryparser/queryparser.lemony:1265 1265 delete *i; Current language: auto; currently c++ (gdb) bt #0 ~TermGroup (yypParser=0x2b58170, yymajor=<value optimized out>, yypminor=0x386a7f8) at queryparser/queryparser.lemony:1265 #1 TermGroup::destroy (yypParser=0x2b58170, yymajor=<value optimized out&...

--- search-xapian/XS/QueryParser.xs | 6 ++++++ search-xapian/Xapian/QueryParser.pm | 7 +++++++ xapian-core/include/xapian/queryparser.h | 3 +++ xapian-core/queryparser/queryparser.cc | 6 ++++++ xapian-core/queryparser/queryparser.lemony | 9 +++++++++ xapian-core/queryparser/queryparser_internal.h | 4 +++- 6 files changed, 34 insertions(+), 1 deletions(-) diff --git a/search-xapian/XS/QueryParser.xs b/search-xapian/XS/QueryParser.xs index 3bec548..78edaaa 100644 --- a/search-xapian/XS/QueryParser.xs +++ b/search-xapian...

Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a

...n AND man Performing query 'Xapian::Query((woman:(pos=1) AND man:(pos=2)))' 0 results found $ python search.py -v woman and man Performing query 'Xapian::Query((woman:(pos=1) AND and:(pos=2) AND man:(pos=3)))' 0 results found In the following code in queryparser.lemony, I think every "term" within if () condition should be changed to "lcterm". I attach a patch file to fix this. } else if (flags & FLAG_BOOLEAN_ANY_CASE) { string lcterm = downcase_term(term); if (term ==...

...-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c queryparser/queryparser_internal.cc -Wp,-MD,queryparser/.deps/queryparser_internal.TPlo -fPIC -DPIC -o queryparser/.libs/queryparser_internal.o /data/home/olly/tmp/xapian-svn-snapshot/tags/1.0.10/xapian/xapian-core/queryparser/queryparser.lemony:25: queryparser_internal.h: No such file or directory /data/home/olly/tmp/xapian-svn-snapshot/tags/1.0.10/xapian/xapian-core/queryparser/queryparser.lemony:31: queryparser_token.h: No such file or directory *** Error code 1 The problem seems to be that the build system is relying on the compiler...

...fix_info of the Term object, it is a vector list, but I don't know when there are multi prefixes for a term?? It leads me to worry about the modifier for multi words, because I only consider the first prefix. --- PATCH CONTENT BEGIN 'queryparser/queryparser.lemon' --- *** queryparser.lemony 2012-01-05 12:28:39.000000000 +0800 --- queryparser.lemony.new 2012-01-05 12:52:56.000000000 +0800 *************** *** 307,316 **** --- 307,318 ---- for (piter = prefixes.begin(); piter != prefixes.end(); ++piter) { // First try the unstemmed term: string term; + #ifndef...

...a new, publically visible, operator to Xapian::Query, I thought I'd better put the patch up for review on the mailing list rather than commit it directly. It's attached to this email, so, comments welcome! -- Richard -------------- next part -------------- Index: queryparser/queryparser.lemony =================================================================== --- queryparser/queryparser.lemony (revision 7552) +++ queryparser/queryparser.lemony (working copy) @@ -148,6 +148,9 @@ add_to_query(q, Query::OP_OR, Query(*t, 1, pos)); ++t; } + if (q.empty()) { + return new Qu...

hi, Olly Betts, Thank you for you answer. My xapian version is 1.2.8. Need I upgrade it to 1.4 if I want to build it with MSVC2017 x64? lishu at fiberhome.com From: Olly Betts Date: 2018-03-29 11:10 To: 李澍; xapian-discuss Subject: Re: how to build 64bit xapian using MSVC2017? On Tue, Mar 20, 2018 at 08:28:24PM +0000, Olly Betts wrote: > Related to this, the appveyor build is

hello everyone, I am Maheshwar, a prefinal year Computer Science undergraduate student at BITS-Pilani, India. When i was going through the GSOC ideas , i felt interested in Quesry parser project. Till now i have implemented a couple of LL(1) parsers as a part of my assignment in Compiler construction course, so i would love to join and contribute to this project. So can any one tell me how to go

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 8186 > Date: 2007-04-11 23:38:53 +0100 (Wed, 11 Apr 2007) > > Log message (7 lines): > queryparser/queryparser.lemony: Fix regression introduced by > Richard's change, and restructure to make the handling for each case > more obvious. Thanks for the catch: I thought I'd avoided breaking anything, but obviously not... My motivation for touching that code at all was that I was trying to implement a...

...dcb0 in Xapian::Database::get_spelling_suggestion (this=0x75b5a8, word=@0xfdcf8998, max_edit_distance=2) at include/xapian/base.h:476 #6 0xfe39ba90 in Xapian::QueryParser::Internal::parse_query (this=0x75b590, qs=@0x798288, flags=128, default_prefix=@0xfdcf8a44) at queryparser/queryparser.lemony:948 #7 0xfe38fa0c in Xapian::QueryParser::parse_query (this=0x798218, query_string=@0x798288, flags=128, default_prefix=@0xfdcf8be0) at include/xapian/base.h:154 #8 0xfe5551f0 in _wrap_QueryParser_parse_query (self=0x0, args=0x712648) at /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/../.....

Hi All, I know that from version 1.2.6, if default_op is OP_NEAR or OP_PHRASE then stemming of the terms is disabled, since positional information isn't indexed for stemmed terms by default. However, I would like to try using OP_NEAR as default_op with stemming because I think the near operator is somehow different from exact phrase. Then I wanna see how the search results looks with this

Hi, Olly: I post the error in the attachment, any methods to fix it? Run the command (.\lemon.exe -q -oqueryparser_internal.cc -hqueryparser_token.h queryparser.lemony) will get the error. If it is hard to fix, I will upgrade xapian to 1.4. But I worry it will cost me too much time to modify my application code. Thanks a lot. Here is the error details: lemon.c: #define LISTSIZE 30 static char *msort( char *list, char **next, int (*cmp)(const char*...

...0 in Xapian::Database::get_spelling_suggestion (this=0x75b5a8, word=@0xfdcf8998, max_edit_distance=2) at include/xapian/base.h:476 #6 0xfe39ba90 in Xapian::QueryParser::Internal::parse_query (this=0x75b590, qs=@0x798288, flags=128, default_prefix=@0xfdcf8a44) at queryparser/queryparser.lemony:948 #7 0xfe38fa0c in Xapian::QueryParser::parse_query (this=0x798218, query_string=@0x798288, flags=128, default_prefix=@0xfdcf8be0) at include/xapian/base.h:154 #8 0xfe5551f0 in _wrap_QueryParser_parse_query (self=0x0, args=0x712648) at /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/.....

...UPPERCASE_LETTER category and indexes this verbatim. However, querying for ??? produces the query Query(???@1). That is, it queries for the lowercase form which seems to be the result of unconditional lower-casing at https://github.com/xapian/xapian/blob/master/xapian-core/queryparser/queryparser.lemony#L1459. As a result, the query returns no result. I have written code that demonstrates this at https://gist.github.com/rsto/168a61536793e10a0a07c3920977e5eb Now, I think that much of this issue can be prevented by normalizing both indexed text and queries before passing them over the Xapian, but...

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect