File list doesn't update until...
The file list does not update after I make an edit until I either click on a file in it or hit the escape key while in the file being edited. In other words, if the current file I'm working on is the eighth one from the top, it stays that way until I take one of the above actions, even though I've made edits. It's been that way through all versions, IIRC. I'm on the latest, 2025.09.21.14.52 on a M4 Mac Mini running OS 15.7.1. It was the same on an Intel MacBook Pro from about 2000, too.
-
Yes.
nvUltra does not reindex a file until you are done editing it – updating the index too frequently can cause a “jitter” in the notes list depending on how fast your computer is, how long it takes the file to be indexed, etc.
0 -
Thanks for clarifying, Fletcher.
What's bothersome about this is that sometimes I'll finish editing a file, then click on another one in the file list to work on that. Because the file list is then updating, I'll often enough find myself in a file other than the one I'd clicked on or intended to click on. I've hit the target, but the target moved so I find myself in a file I didn't want to be in. Easily enough resolved, I know. Just click on the desired file in the now stable file list.
What about something like a check at some amount of time after keystroke input, something relatively long like 2-4 seconds? Then, if there haven't been more keystrokes, the file list can reindex. Or whatever other technique. It's the click on the moving target that's the problem. That way, if I stay in the same file for awhile longer, the file list will be up to date so that clicking on another file would be less likely to result in inadvertently clicking the wrong one.
I'll leave this alone now. :)
0 -
Let me look into some options.
Thanks for clarifying the further details!
0 -
Thanks, Fletcher!
0 -
Just thinking about this after running into the situation I described above with clicking on a file in the file list only to miss it because it moved… What do you think about this approach? The user makes an edit, the first keystroke. If the current file is not on top of the file list, then update the list. If the file is on top of the list, don't reindex. Once the user has made a single character change, the file will move to the top, so further editing won't need to refresh the list. That should avoid the jittering problem.
Not that I'm privy to what's under the hood here along with the larger code picture. Just a thought, though. No pressure intended.
0 -
The latest release allows indexing the currently edited file. We'll see if any new issues arise as a result.
Thanks!!
0 -
Great! I'll let you know if I see any problems. So far, so good.
0
Please sign in to leave a comment.
Comments
7 comments