date wrote:Highlighting in the main screen does not work when only one character has been typed.
Confirmed, will be fixed, thanks.
date wrote:When the note contains the text -> 09/html : example <-, 9*e does not find the note, both the main screen and the note window. (But it did find other notes containing something with 9 --> e.)
Well this is by design: the pattern is broken by whitespace characters. Otherwise totally unexpected matches will be possible, because paragraphs can be quite long!
date wrote:In the note edit window specifically, if the note contains just the word -> example <-, 'Find Next' will not find anything when you search for 'e.' 'Find Before' finds only the last 'e.' (With wildcards and 'in words' selected.)
Reproduced, this is indeed a bug, will fix. Thanks!
date wrote:In another note, which I can't find anymore this quickly, it would find occurences with 'Find Next' until the end, and then stop, while 'Find Previous' would continue from the end to the start and again continuously.
Would be so great to repro this. Any chance you could come up with sample data for this?
date wrote:But in general, it appears to work very well.
Glad to hear, especially from you!)
Since this version (after 3.9 b2) I can't clip anymore as it inserts plain html. I use Firefox 50, but I briefly tried Vivaldi, and it appears the clipping really is broken.
Unselecting one of 'retain rtf' or 'retain html' did not help. (Except for not clipping with links of course.)
Confirmed. That's my fault - I tested on a too old version of Firefox, should have tested on the recent one. Will fix this asap!
date wrote:I don't understand completely, but it sounds like a bad idea. 'Whole words only' means it will not find anything until after the whole word has been typed. 'Search inside words' otoh is plain and simple english?
Yes. but now you can use wildcards and add * at the end to find incomplete words. On the other hand, currrently finding notes with only "the" but without "there", "there's", "thereof" etc. is very problematic. "Whole words only" will make this easy.
date wrote:There's also the option 'search across boundaries.' It's function is difficult to grasp, and the performance benefit when turned off is minimal to non-existent. If it's faster, is't faster at not finding anything. I'd rather suggest removing that one and make it the standard behavior.
More or less I can agree. Does maybe anyone object to removing this option and making the "on" state the default one?