Would be nice if they could figure out a way to print or export both PDF and notes panes simultaneously i.e. with highlights positioned in or near the margin of the PDF text. Present separation makes it difficult to share notes with their context intact.
Excited for the upcoming content. Although I now mainly use Obsidian, this kind of content and workflow walkthrough makes me want to tinker with Logseq again and again.
Greate runthrough, thanks. Many users hate the idea of an auto-create page for a property. It's currently bugged. Except for tags:: and alias:: a single value doesn't create a page:- 'somekey:: value1'. If you add a comma it creates a page:- 'somekey:: value1,' and a list will create a page for each value:- 'somekey::value1, value2'. Those who don't like this polluting the graph and want to keep properties for queries will need a setting to turn this off. At present, if I don't want an auto-create page in my graph I have to use the page-property exclude-from-graph-view.
It's an interesting conundrum - ideally this would be the sort of thing that one could toggle on and off, but I imagine that would add significant dev burden 🤔
@@CombiningMindsPKM I would hope not unless the codebase is poor. I spent 35 years developing in c/c++ so I have been studying Clojure to help with advanced queries. Just downloaded the source code to have a look although I'm not yet fluent at reading Clojure.
@@CombiningMindsPKM `{{query property property_name property_value}}` on its own will retrieve the top-level block containing the property, but adding boolean `and` for tags, links or "text" in subordinate blocks returns nothing at all. It would seem that both parameters of the `and` statement need to be located at the same block level? Re-indexing done.
how do you deal with duplicate links references? I often will have linked reference duplicates because I link words inside a block that was already previously linked with that word in it's title. I do this to better label everything with whatever applies, and to link any mentions throughout text to make navigating at the speed of thought easier. But the more I link, the more cluttered my linked references become with duplicates. Is there a way to deal with this? Maybe a way to not show linked references if they already appear in another linked reference? I'd really appreciate your input on this, I am LOVING LogSeq and your videos are instrumental in helping me use it to it's fullest extent.
Thanks for the feedback. Unfortunately this is not something I've encountered in my own workflow, so I'm not sure how best to provide input. My general advice would be to only link the part that you want to show up in your linked references. In that case, not linking the word in the title might be the best approach, but it really depends how you want to resurface that information, and how you want it to display in your linked references.
Hi Dario! Thank you for your awesome videos! Could you elaborate on what you mean by "cluttering the database" with pages (starting at 07:45)? My biggest struggle with using Logseq is deciding when to use the daily journal or writing on a dedicated page.
Hey :) Readwise exports articles as pages, which creates a proliferation of "nodes'' in your database as these are all separate files. I think the most scalable solution is to use blocks. For writing, my approach is to use the daily journal and tag the blocks well. I then simply move those blocks into dedicated pages at a later stage when I am writing about a certain topic. Hope that helps :)
Hello, A more important feature than the inline reference would be to view the embedded blocks from which page they were embedded. Now the original context of the embedded block is not visible, unfortunately. Therefore, in the case of embedded blocks, one would need to find out where they came from and from which page they were embedded. In Roam, it works fine. So it would also be nice to see where the embedded blocks came from and where they were embedded in Logseq. I guess the original page should be listed as the first reference. I wonder how difficult this is to develop, but it seems straightforward.
I see what you mean. Not being able to see the source inline is somewhat limiting. You can always open the block and see the breadcrumbs, but that requires a few more clicks unfortunately.
hmm. It looks like the properties values popup only appears when you first enter :: and select a property from that popup. What if you use a template that already includes all the property types you want for the page? There doesn't seem to be a values popup in that case.
I'm not sure how the properties are saved in the files, but I imagine that the way to instantiate a property is the same (speaking under correction though)
@@CombiningMindsPKM That’s ok. Everyone has its own experience. No judgments, just being friend one to another is what really counts. What a great work you do teaching about Logseq! Thank you brother!
Hi, nice to see your get a hair cut :P haha, (no joking ;) ) . But I had a question. Last I showed a teacher LogSeq, and she was really enthusiastic. Because of the pdf tekst link things en the Flashcards. But then she asked, how can I share this easy to a student or college. And that I react, i don't know how to do that Easily. So how is that possible, in a way that also contains the "uploaded" pdf files, and created tags... Thanks!
Hey - I quite like the haircut 😋 She could share the whole folder on a shared drive for the students, and everyone should be able to access it that way.
@@CombiningMindsPKM Aha, but then everyone should have LogSeq installed, right? But what if that isn't the case(?) Or is there a working together function, like office, in a browser ofzo?
A lot of very interesting insights. Logseq is one of the best tools. I tried Obsidian and it seemed bloated and wasn't aesthetically pleasing. Logseq is great.
@@dennismaorwe I have no idea unfortunately. I think it will still be a while, as there are many features still in alpha development (real-time collaboration, whiteboards)
Thanks! Best Logseq video ever!
Thanks Jon! I appreaciate your generosity 🙏🏽
PDF support of logseq is unbeatable!
Getting there at least!
Would be nice if they could figure out a way to print or export both PDF and notes panes simultaneously i.e. with highlights positioned in or near the margin of the PDF text. Present separation makes it difficult to share notes with their context intact.
I need to print a PDF directly from Logseq as well.
@@juergenheise28 I think there are some plugins that allow for that.
Please add epub support
12:08 that is such a nice list of intentions, bless you up sir
🙏🏽
Thanks
Thanks for the support :)
Excited for the upcoming content. Although I now mainly use Obsidian, this kind of content and workflow walkthrough makes me want to tinker with Logseq again and again.
There's a cool one coming up on using the two together :)
I really appreciate you making these videos! Just got some great ideas on how to structure my uni notes a bit better :)
Glad to have helped :)
Nice to see you back! You look different 🤪
Thanks 🙏🏽 The one constant in life is change 😅
Greate runthrough, thanks. Many users hate the idea of an auto-create page for a property. It's currently bugged. Except for tags:: and alias:: a single value doesn't create a page:- 'somekey:: value1'. If you add a comma it creates a page:- 'somekey:: value1,' and a list will create a page for each value:- 'somekey::value1, value2'. Those who don't like this polluting the graph and want to keep properties for queries will need a setting to turn this off. At present, if I don't want an auto-create page in my graph I have to use the page-property exclude-from-graph-view.
It's an interesting conundrum - ideally this would be the sort of thing that one could toggle on and off, but I imagine that would add significant dev burden 🤔
@@CombiningMindsPKM I would hope not unless the codebase is poor. I spent 35 years developing in c/c++ so I have been studying Clojure to help with advanced queries. Just downloaded the source code to have a look although I'm not yet fluent at reading Clojure.
Any suggestions on how to query block level properties and tags/links in subordinate blocks at the same time?
@@anydroid using Boolean logic should work for this? (i.e. {{query (and (property property_name property_value) [[tags]] )}} ?
@@CombiningMindsPKM `{{query property property_name property_value}}` on its own will retrieve the top-level block containing the property, but adding boolean `and` for tags, links or "text" in subordinate blocks returns nothing at all. It would seem that both parameters of the `and` statement need to be located at the same block level? Re-indexing done.
how do you deal with duplicate links references? I often will have linked reference duplicates because I link words inside a block that was already previously linked with that word in it's title. I do this to better label everything with whatever applies, and to link any mentions throughout text to make navigating at the speed of thought easier. But the more I link, the more cluttered my linked references become with duplicates. Is there a way to deal with this? Maybe a way to not show linked references if they already appear in another linked reference? I'd really appreciate your input on this, I am LOVING LogSeq and your videos are instrumental in helping me use it to it's fullest extent.
Thanks for the feedback.
Unfortunately this is not something I've encountered in my own workflow, so I'm not sure how best to provide input.
My general advice would be to only link the part that you want to show up in your linked references. In that case, not linking the word in the title might be the best approach, but it really depends how you want to resurface that information, and how you want it to display in your linked references.
Hi Dario! Thank you for your awesome videos! Could you elaborate on what you mean by "cluttering the database" with pages (starting at 07:45)? My biggest struggle with using Logseq is deciding when to use the daily journal or writing on a dedicated page.
Hey :)
Readwise exports articles as pages, which creates a proliferation of "nodes'' in your database as these are all separate files. I think the most scalable solution is to use blocks.
For writing, my approach is to use the daily journal and tag the blocks well. I then simply move those blocks into dedicated pages at a later stage when I am writing about a certain topic.
Hope that helps :)
Hello, A more important feature than the inline reference would be to view the embedded blocks from which page they were embedded. Now the original context of the embedded block is not visible, unfortunately. Therefore, in the case of embedded blocks, one would need to find out where they came from and from which page they were embedded. In Roam, it works fine. So it would also be nice to see where the embedded blocks came from and where they were embedded in Logseq. I guess the original page should be listed as the first reference. I wonder how difficult this is to develop, but it seems straightforward.
I see what you mean. Not being able to see the source inline is somewhat limiting. You can always open the block and see the breadcrumbs, but that requires a few more clicks unfortunately.
hmm. It looks like the properties values popup only appears when you first enter :: and select a property from that popup. What if you use a template that already includes all the property types you want for the page? There doesn't seem to be a values popup in that case.
True, it only works when you type the colons at this stage. Hopefully there will be further improvements that allow for that in the future.
Will be the properties stay the same in org-mode?
I'm not sure how the properties are saved in the files, but I imagine that the way to instantiate a property is the same (speaking under correction though)
0. Hairstyle
Jokes aside, have you tried the upcoming whiteboard feature? It's a game changer for me.
😋 I have played with it a little, but keeping it off the channel until it's out of alpha 🙂
Amazing! What meditation course? Vipassana?
Yep, it was a Vipassana course with Goenka :)
@@CombiningMindsPKM wow! great! I did it too! No words to describe. Be happy! 👊🏽
@@paulobehar Haha, the first time was an amazing experience, but I didn't find the second time as valuable 😑
@@CombiningMindsPKM That’s ok. Everyone has its own experience. No judgments, just being friend one to another is what really counts. What a great work you do teaching about Logseq! Thank you brother!
{{namespace page}} can not render
Are you using the latest version? (0.8.8)
Hi, nice to see your get a hair cut :P haha, (no joking ;) ) .
But I had a question. Last I showed a teacher LogSeq, and she was really enthusiastic. Because of the pdf tekst link things en the Flashcards.
But then she asked, how can I share this easy to a student or college. And that I react, i don't know how to do that Easily. So how is that possible, in a way that also contains the "uploaded" pdf files, and created tags...
Thanks!
Hey - I quite like the haircut 😋
She could share the whole folder on a shared drive for the students, and everyone should be able to access it that way.
@@CombiningMindsPKM Aha, but then everyone should have LogSeq installed, right?
But what if that isn't the case(?)
Or is there a working together function, like office, in a browser ofzo?
❤
A lot of very interesting insights. Logseq is one of the best tools. I tried Obsidian and it seemed bloated and wasn't aesthetically pleasing. Logseq is great.
Thanks :) The 'plug-and-play' nature of Logseq is a big win.
I'm using Obsidian. It is very beautiful. Just find the theme you prefer.
You've cut your hair since recording Logseq mastery.
Indeed - may have to do a re-recording when Logseq officially comes out of beta 😋
Might we know that could be?
@@dennismaorwe I have no idea unfortunately. I think it will still be a while, as there are many features still in alpha development (real-time collaboration, whiteboards)