Searching words with swedish characters stopped working
Completed
Hi,
Searching words with swedish characters has stopped working with the latest update, that is words containing
åäö och ÅÄÖ
Finding a file and retyping the letters seem to fix, but it is of course impossible across 1200 files.
The bug is in Version 1.0.0 (2022.12.23.14.53) but can have appeared previously, since I have a memory of not getting the results I searched for earlier in december. I do not remember when I updated last before the 2022.12.23 version.
-
Can submit a support request with a sample file that does not work, along with exactly what you type in the search bar?
I suspect this may be an issue with text that looks the same, but actually is composed of different characters "behind the scenes". I need a good test to identify the issue and fix it.
Thanks!
0 -
I have (hopefully) submitted a request! Thanks for the swift reply. Do you ever sleep? :-)
0 -
Close all windows in nvUltra, then in the general preferences use the "Clear cache" button. This will force all folders to be reindexed. See if that fixes it.
When I add your file to a folder and copy/paste your search terms from the support ticket, it works just fine.
0 -
Windows closed. Cache Cleared. (Althought there is no indication of success apart from the button being pressed. Where is the cache file located?) nvUltra restarted.
Reindexing starting... and going on for five minutes now. Is this normal? This is the indexing process line showing, right? So far I can not search for anything.
0 -
I think you have a file with invalid characters that is preventing the index from being updated. The next update fixes this.
This should only happen if a file gets corrupted, or if you give a text file extension to a file that contains binary (non-text) information.
0 -
In the meantime, to get indexing to work you need to remove the troublesome file(s) from the folder in order to allow the other files to be indexed.
0 -
Cleaned up some debris from over the years, and now only .txt and .md files left, same problem. Is there another way to find the culprit apart from waiting for the next update? I guess I could do a grep or something, but since I don't know what character I'm looking for... :-)
(It's OK, I've still got nvALT, so I'm not in any hurry.)0 -
You have to try taking out half the files and see if it succeeds. Recursively add or remove half of the half until you narrow it down.
0 -
Yes, of course, recursive search. Sorry, it's been maaany years since I did any programming. I had two culprits with what looked like 16-bit unicode in places where once had been [åäö], but neither MacVim or UltraEdit could read the characters correctly.
Problem gone, search now working as expected. Thank you, Fletcher!
0 -
When I first saw that approach to searching for problems (Conflict Catcher for classic Macs years ago), I thought it was absolute genius.... ;)
Glad you found the issue, and glad it confirmed what I was thinking. I thought that search was implemented correctly in the latest public build, but the indexing of invalid files has not been released publicly yet.
I'm trying to fix a more insidious issue with indexing and maintaining the filtered list of notes in the table for the next release so I can a few things released all at once, hopefully later this week.
0
Please sign in to leave a comment.
Comments
10 comments