Displaying 8 results from an estimated 8 matches for "search_or".
2019 Jan 12
2
Solr -> Xapian ?
...rn "C" {
>> + #endif
>
> You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this.
>
>> 1 - WHat does represent "subargs" in mail_search_args
>
> It's set only for SEARCH_OR and SEARCH_SUB. So for example:
>
> SEARCH TEXT foo TEXT bar TEXT baz
>
> results in:
>
> type=SEARCH_SUB
> value.subargs = (
> { type=SEARCH, value.str="foo" },
> { type=SEARCH, value.str="bar" },
> { type=SEARCH, value.str="baz" },
&g...
2019 Jan 12
2
Solr -> Xapian ?
...s
> + extern "C" {
> + #endif
>
> You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this.
>
> 1 - WHat does represent "subargs" in mail_search_args
> It's set only for SEARCH_OR and SEARCH_SUB. So for example:
>
> SEARCH TEXT foo TEXT bar TEXT baz
>
> results in:
>
> type=SEARCH_SUB
> value.subargs = (
> { type=SEARCH, value.str="foo" },
> { type=SEARCH, value.str="bar" },
> { type=SEARCH, value.str="baz" },
&g...
2019 Jan 12
0
Solr -> Xapian ?
...def __cplusplus
> + extern "C" {
> + #endif
>
You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this.
> 1 - WHat does represent "subargs" in mail_search_args
It's set only for SEARCH_OR and SEARCH_SUB. So for example:
SEARCH TEXT foo TEXT bar TEXT baz
results in:
type=SEARCH_SUB
value.subargs = (
{ type=SEARCH, value.str="foo" },
{ type=SEARCH, value.str="bar" },
{ type=SEARCH, value.str="baz" },
)
Or similarly if there's SEARCH OR foo O...
2019 Jan 12
0
Solr -> Xapian ?
...s
> + extern "C" {
> + #endif
>
> You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this.
>
> 1 - WHat does represent "subargs" in mail_search_args
> It's set only for SEARCH_OR and SEARCH_SUB. So for example:
>
> SEARCH TEXT foo TEXT bar TEXT baz
>
> results in:
>
> type=SEARCH_SUB
> value.subargs = (
> { type=SEARCH, value.str="foo" },
> { type=SEARCH, value.str="bar" },
> { type=SEARCH, value.str="baz" },
&g...
2019 Jan 13
0
Solr -> Xapian ?
...s
> + extern "C" {
> + #endif
>
> You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this.
>
> 1 - WHat does represent "subargs" in mail_search_args
> It's set only for SEARCH_OR and SEARCH_SUB. So for example:
>
> SEARCH TEXT foo TEXT bar TEXT baz
>
> results in:
>
> type=SEARCH_SUB
> value.subargs = (
> { type=SEARCH, value.str="foo" },
> { type=SEARCH, value.str="bar" },
> { type=SEARCH, value.str="baz" },
&g...
2009 May 19
2
expire-tool segmentation fault
Hi!
I'm using Dovecot 1.1.15 on OpenBSD 4.4.
How can I debug this?
# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-
tool
Segmentation fault (core dumped)
# gdb /usr/local/sbin/dovecot
(gdb) run --exec-mail ext /usr/local/libexec/dovecot/expire-tool
Starting program: /usr/local/sbin/dovecot --exec-mail ext
/usr/local/libexec/dovecot/expire-tool
Program received
2019 Jan 11
4
Solr -> Xapian ?
The below patch resolves the compilation error
$ DIFF -P COMPAT.H COMPAT.H.JOAN
*** compat.h 2019-01-11 20:21:00.726625427 +0100
--- compat.h.joan 2019-01-11 20:14:41.729109919 +0100
*************** struct iovec;
*** 202,207 ****
--- 202,211 ----
ssize_t i_my_writev(int fd, const struct iovec *iov, int iov_len);
#endif
+ #ifdef __cplusplus
+ extern "C" {
+ #endif
+
#if
2019 Apr 21
2
FTS delays
It's because you're misunderstanding how the lookup() function works. It gets ALL the search parameters, including the "mailbox inbox". This is intentional, and not a bug. Two reasons being:
1) The FTS plugin in theory could support indexing/searching any kinds of searches, not just regular word searches. So I didn't want to limit it unnecessarily.
2) Especially with