I have considered what to do with something like that before.
There is a bunch of solutions like maybe regex, but most standard users will likely never know how it works.
Probably the easiest to add, but I dont like the fact it will be difficult to learn.
Or just be smart about if 2 words are used, like Google does. If the words are found together put the result at the top, if they are split put them as secondary answers, plus you could do a bunch more smart things etc.
In reality Sqlite has all kinds of things built in that would make this work amazingly well and easy.
The never completed Tuniac 2 used sqlite for its db, Tuniac 1 uses a custom very basic db.
So to implement this the way I would want would mean switching Tuniacs db to sqlite.
And that scares me.
It would take me ages and it has taken 10 years to get Tuniac to this fairly bug free point, this change would likely reset that clock.
In 2025 I will still be finding random things I broke in the db changeover.
A more skilled dev would likely knock out the code in a few days and it would be bulletproof.
My day job is PABX's not computer programs, I learned how to read/write c/c++for Tuniac by working on Tuniac.
The reason nothing really changes is that Tuniac needs an actual programmer to make significant changes.
Sqlite would speed up load times, speed up save times, prevent corruption if a single failed write eg power out during write, speed up lookups in the db, give advanced text searching, allow third party apps to use generic ways to read/write to Tuniacs db and likely a bunch more.
It is the answer, it just needs a motivated dev to implement
