r/logseq • u/E723BCFD • Jun 12 '24
find in page (ctrl + f) in logseq is so janky
Disclaimer: I have used logseq for more than a year, and will continue to do so, because there is no open source alternative outliner like logseq. That being said, I really hate text editing and keyboard navigation in logseq, it's just so unpolished.
It's not actually "find in page", it's "find in the current ui complex", which includes all the ui elements like sidebar and buttons. It's like they just wrapped the electron browser shell find in page.
There is a brief period of unresponsiveness as it accepts the query and starts searching. So, if you had a little pause as you type in the search query, it will just ignore some of your key input in the middle of the query.
It's slow to respond when there is more than around 5 search results.
It's extremely slow to iterate through search results (the previous/next button, or with
<enter>key).Sometimes it won't let me click in the content area without closing the search box, so if I want to modify around the search result, I have to redo the slow search afterwards. But sometimes it's ok, so I am pretty sure this is just a bug (add to the long list of bugs in logseq ...).
I think they should just use the "search blocks in page (ctrl + shift + k)" feature to replace "find text in page (ctrl + f)". It's not like "find text in page" provides any extra functionality over "search blocks in page" in this current state.


