On the one hand, I would also like to see a direct reaction from the development team here in the forum more often - on the other hand, I’m glad when they use their time to move LOGseq forward.
Even if they don’t speak out so often in the forum, some bugs that got reported here got actually fixed. That’s why I remain optimistic that it helps if we draw attention to problems that are important to us here in the forum.
This is an amazing post! Thanks so much for compiling this, we’ll use it as our main reference to improve search here. So sorry for the lack of responsiveness! We working to be more active here on the forums, and everyone on the team is reprioritizing to do so. Expect us to be way more active on here from now on
Hard to prioritize with such a small team, and we’re getting better at it. But lately we’ve been focused on the loudest asks (mobile, sync) and the most critical bugs (anything that touches data loss). Sorry for not keeping up! Just hired someone to work on search, so expect improvements here
I am also referencing the issue of not jumping to blocks when in search, as mentioned here:
Interestingly, on the web version there is no such issue. Even with the updated (Beta) local version this issue persists.
Thank you @ianmcn for implicitly suggesting another workaround of creating a page and looking for unlinked references.
Also, I would love to search for posts from certain time-frames (I personally organize my life in terms of notes by the places where I live). Thus, for example, being able to look for “What a wonderful world” between 2021-03-17 and 2021-05-23 would be great.
I have not yet been able to make this work through queries. If someone reading this knows a workaround, please let me know!
I am looking forward to the work of the new hire focusing on search @ andotvu !