search top level using ââ example âwillâ
Only will not willing should be returned
Seem to be known that it does not work but I cannot find it reported as a bug, guess it is now.
Would be nice to have it working as per the manual
search top level using ââ example âwillâ
Only will not willing should be returned
Seem to be known that it does not work but I cannot find it reported as a bug, guess it is now.
Would be nice to have it working as per the manual
Thatâs how search normally works. Notepad, Google Docs, etc, all work that way.
Itâs normal and expected.
If you want to exclude stuff, you can use a minus sign, search âwillâ -âingâ for example. Or if you expect it to be in the middle of a sentence you could include the space before or after, or both, " will ".
Hi Thanks, I was aware
Yet Gmail (searching through a list of items) supports exact.
Excluding in a decent sized Dynalist is not practical. My assistants name is Di that occurrence is just far to common.
I see what you mean. I agree. Itâd be better if anything in quotes was an exact Whole Word Only search rather than exact substring search. I see google products do it that way, and I know Microsoft Word has a âWhole Words Onlyâ checkbox to make it work that way. I canât think of any issue if it worked that way. The developers probably just didnât get around to making a more advanced algorithm. I would call it a Feature Request rather than a bug, though.
In the mean time you probably will want to find yourself a workaround like using a more unique name like #Di or @Di or searching with the trailing space within the quotes "Di " so at least it doesnât match âDinosaurâ etc.
As my old boss used to say, write the manual before writing the code, then it is always clear what a bug is
Will move Di to @Di I guess but two and 3 letter combos in a list are always going to multi match
Thanks and Regards
Itâs ambiguous - I didnât read it that way. The manual only says exact, so "will"ing is an exact match, but an exact substring, rather than Whole Word Only (exact + word boundary on both sides). So, everything in quotes works the same way that Microsoft Word searches when you donât select the advanced option. And then spaces outside of quotes are used as AND operators. It makes sense they did it that way, since javascript works that way (substring search), and you need more lines of code for word boundary.
But, I agree it would be better working your way. Bug or Feature Request, whatever.
Thanks for your input