You see it is so rare to have the possibility/chance to "talk" to the actual developer (actually that is quite easy, having the developer listening and reply is the difficult part ) that I tend to overload the unfortunate guy that actually accepts entering this kind of discussion with ideas/feature requests/etc., of course there is no "deadline" or expected *anything*, just ideas that you are perfectly free to ignore if you find them leading the tool on a different path from what you designed or if it is too complex (or whatever).
About regular expressions, iMHO they are useful, only still IMHO and providing for the sake of the example completely faked data they won't be used by - say - 82.74% of the "intended audience" of the GUI version (that has them) while the 97.14% of the (much less) users of the command line tool (which has not them) would find them very useful and actually use them.
I'll check if I can "separate" the two apps, thanks.
JFYI, Everything has a different approach, it makes a "own" index of all files on the volumes and then searches for files in this index, whilst Swiftsearch - if I get this right - directly parses the $MFT of the NTFS volume.
There are of course advantages and disadvantages of each approach, but AFAICT Swiftsearch seems like a "more portable" approach.