2MB!!)
fossil search -a "scroll*"
works fine for me
> -Original Message- From: Richard Hipp
> Sent: Tuesday, November 17, 2015 6:03 PM
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] FOSSIL SEARCH improvement suggestion
>
> On 11/17/15, Ton
This worked (and I without the Porter Stemmer 'bloat'). Thanks.
-Original Message-
From: Michael Keuter
Sent: Tuesday, November 17, 2015 6:10 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL SEARCH improvement suggestion
Am 17.11.2015 um 17:03
ber 17, 2015 6:03 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] FOSSIL SEARCH improvement suggestion
On 11/17/15, Tony Papadimitriou wrote:
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and
vice versa.
"scroll" should match "scroll
Am 17.11.2015 um 17:03 schrieb Richard Hipp :
> On 11/17/15, Tony Papadimitriou wrote:
>>
>> So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and
>> vice versa.
>
> "scroll" should match "scrolling" if you activate the "Porter Stemmer" option
Or 'scroll*' :-).
Michael
On 11/17/15, Tony Papadimitriou wrote:
>
> So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and
> vice versa.
>
"scroll" should match "scrolling" if you activate the "Porter Stemmer" option
--
D. Richard Hipp
d...@sqlite.org
___
When using SEARCH you need to type the word exactly as it appears in the
timeline.
I’m guessing it uses SQL’s LIKE to find the related matches.
So, if you’re looking for the word ‘scroll’ it won’t match ‘scrolling’ and vice
versa.
One suggestion is to append ‘%’ to the search term to match any
6 matches
Mail list logo
