I have to say that logseqs feature set looked enticing half a year ago when I started to use it. It still looks enticing, if only because I am no nearer to actually use these capabilities:
For fun (and to learn), I am trying this:
- Sprinkle three-line-blocks like “[[expense]]”, “category:: foo”, “amount:: 20” throughout my journals.
- Create a query that collects all these blocks and presents the categories and amounts in tabular form.
- Have a sum of the amounts underneath the table.
- And as a stretch goal, group the table rows by category and produce sums by group.
So we start with {{query (and [[expense]])). Fine. Now it is time to add two lines to the query block that I cribbed from somewhere else: “query-table:: true” and “query-properties:: [:category :amount]”.
Next: as a child of the query, add “{{function (sum :amount)}}”.
At that point, just as I hit the TAB key to demote the new block after the query block, Logseq eats the two properties I just entered. I was going to attach a short (35 sec) video, but .mkv and such are not authorized.
Much worse, though, is that Logseq is actively user-hostile. Pretty much nothing is “discoverable”, there is no printing, no decent export to PDF (yes, I tried the plug-ins), no intruduction for people like me who look for a tool and not for a hobby.
I may have to go back to Onenote. Much less powerful, but what there is works and is easy to use – it helps me working instead of becoming this huge time-suck.
Cheers,
Felix.