Currently, History (Search History) is stored case sensitive.
Would it make sense for it to be stored cased insensitive?
As it is, 'Jethro Tull' & 'jethro tull' are stored (& counted) separately.
Results returned do not appear to be affected (that I'm seeing) by case?
(Well unless case: nocase: are specified.
Perhaps only store History with case sensitivity if case:/nocase: are specified?
But then case: itself is already store in History, I think?)
History, case-insensitive
Re: History, case-insensitive
Currently, search history is case sensitive.
I'll consider storing search history as lower case (or add the option to do so).
Thanks for the suggestion.
I'll consider storing search history as lower case (or add the option to do so).
Thanks for the suggestion.
Re: History, case-insensitive
If History is insensitive, what do you do on odd time when you use a case: modifier in your search?
Might be an odd occurrence, but it is one case where sensitivity matters.
(That said, I'm still for insensitivity.
Rather not have everything revert to lower case, as at times, I'll particularly want to see certain items displayed case sensitive.
In particular with drive letters or particular directory names; so.
Not a big deal, just helps things to stand out.)
case:case
case:CASE
Might be an odd occurrence, but it is one case where sensitivity matters.
(That said, I'm still for insensitivity.
Rather not have everything revert to lower case, as at times, I'll particularly want to see certain items displayed case sensitive.
In particular with drive letters or particular directory names; so
C:/ TMP .sqlite
Not a big deal, just helps things to stand out.)
Re: History, case-insensitive
The latest search could update the search history to the correct case.If History is insensitive, what do you do on odd time when you use a case: modifier in your search?
case:case
case:CASE
Only one of the case:abc or case:ABC search history entires could exist at one time.