ANGRYsearch
ANGRYsearch copied to clipboard
DoTheEvo
Forbidden Characters in Search
Not sure if this is an ANGRYsearch problem or something in the underlying FTS setup but words/filenames including some rather common characters don't appear when searching. A file called "Mom's Recipes.txt" won't appear if you search for "Mom's" as it doesn't seem to like the apostrophe. Works in full mode but not lite.
Thus far I've noticed the following characters don't work: ' - ; : #
Just wondering if these is fixable or if it's a feature of the search methods employed.
Fast search mode uses special functionality of sqlite database and some additional special tables in it, so it seems that many special characters dont work in that mode.
Also single quotation marks(apostrophe) are used for exact whole word searches, 'pass' would not show results containing word password
the minus or dash - is used in fast mode to exclude some term from results , so config -home would exclude any item from search results that has home somewhere on its path. But thats only working on Archlinux now, since its sqlite packages has FTS5, while most distros are on FTS4
others are just not working, few versions ago they were crashing the angrysearch...
Slow mode, with checkbox unchecked searches it all as plain text, no special indexing and extra tables... so that helps when in need
Thought it might be due to FTS; no way to escape said characters or does FTS just not consider them at all?
Dash functionality does seem a little off as it seems to use it even if it's within a term ('config-home' vs 'config -home') but guessing that's again due to the functionality in SQLite? Or is it perhaps how the terms are being split?
(as an aside minus/dash also appears to be working on Ubuntu 14.04.5 as that's what I'm testing on and it certainly seems to be excluding terms)
no way to escape said characters or does FTS just not consider them at all?
I think so, but can check when feeling like it.. I dealt with it some time ago... letting apostrophe work if it can and only use double quotation marks for exact search would not be a worse idea, if possible
Dash functionality does seem a little off as it seems to use it even if it's within a term ('config-home' vs 'config -home') but guessing that's again due to the functionality in SQLite?
FTS is not a problem in that case, I just used dash in angrysearch for additional functionality. Search terms are split by space, then if some starts with - it gets added to the excluded list
Normal use of dash within words should work fine
(as an aside minus/dash also appears to be working on Ubuntu 14.04.5 as that's what I'm testing on and it certainly seems to be excluding terms)
you can check FTS version by hovering mouse over middle bullet point item in update. I just checked in virtual box ubuntu 16.04.1and excluding with dash does not work for me at all.
while on arch it works
What The Fuck
well... I installed 14.04.5 and yes, its confirmed, behaves exactly like yours but I have no idea why, I checked and that FTS4/FTS5 detection behaves correctly, its not thinking its on FTS5. It is following the expected behavior, and its queries are correct.
My guess is that ubuntu 14.04 must have its sqlite3 compiled with some extra flags or some additions or some shit. That config-home results are also all kinds of wrong...
luckily its all in the past, and I dont have to deal with that, and it should work fine just that dash character is being wonky...
Search works with apostrophes at the end of words but not in the middle of words.
