Logseq Query Builder Quick Look
Вставка
- Опубліковано 9 лип 2024
- It's finally here!
💌 Join my mailinglist - toolsontech.ck.page/
💖 Let me know you want more, subscribe
Help me fund my Logseq Addiction and make more videos - / toolsontech
==== 👋 Contact 👋 ====
Website - toolsontech.com/
LinkedIn - / basgrolleman
Twitter - / toolsontech
==== 🏅 Licenses 🏅 ====
Storyblocks for Music and Stock footage, Flaticon for Icons and Giphy for Animated Gifs
Chose the right time to get back to Logseq! Thanks for the info
For sure, this makes writing quick queries so much easier.
The funny thing is, now that I started mastering my queries, I am a bit sad that they made it so easy. 😂
It is really handy to have a query builder at hand. Queries were the thing that drove me away from Logseq a while ago. Won't happen again for sure!
Luckily it's mostly a selector on the same system, so all the knowledge is still useful. I'll probably keep writing a lot of them as well, sometimes it's just faster.
Thank you
More soon, queries really unlock the power of all those logseq notes. :)
@@toolsontech Yes, I heard you were making a video. I'm really looking forward to it. :)
Thanks! Is it only possible to use AND or are NOT and OR also included in this builder?
Also not and or are included
Yup, they work. Messing around with them now as it requires a bit of finesse to use.
I love Logseq and this is a great start. But god development is soooo slooooowwww compared to the competition. In general we need much more polished functionality and faster delivery time…
Main reason development is slow is because they are working on a redesign. Most projects go through that at some point, where you have to look at the foundation and change it so it can handle the long term growth.
Once that's out, expect much better speed in development.
@@toolsontech I have also heard the opinion that the need to support md and org slows down development a lot. This imposes a certain limitation and burden on the development team.
@@tonyatlas5653 True, that's a problem you can solve because only a small part of syntax is md/org specific. Would be better if it was a switch though, that way you don't have to monitor for conflicts. (Like * being a heading in org mode and a bullet point in markdown)
@@tonyatlas5653 imo they should just jettison md. This project has its origins in org.