Great idea. An goal that can easily be achieved in the near future is the above: specifically, to be able to open a Logseq markdown file in Obisidan, and being able to make limited edits in Obsidian within the Logseq-generated structure, and being able to open it back in Logseq. Things that are blocking it today:
Logseq uses headings (#), instead of bullets (-)
Logseq doesn’t “cleanly” separate directory structure from config
this might just amount to renaming the config directory to “.logseq”
can Obsidian be told to ignore the .logseq directory?
How does Obsidian handle block metadata generated by Logseq?
How does Obsidian handle frontmatter generated by Logseq?
As soon as plugins, themes, etc. became a part of Logseq, I have been thinking wouldn’t it be nice to just drag n drop an Obsidian.md. theme and use it in Logseq. I know this is not how things work and it’s not that easy. But wouldn’t it be nice.
TLDR: Bumping this with the latest state of using Logseq and Obsdian together. I love using both Logseq and Obsidian, but I’m outlining my current gripes that prevent me from being fully happy with the experience. I put these examples together to open source solutions for these issues. Would love to hear how other people integrate the two successfully or if I’m an outlier.
I use Logseq as an outliner and Obsidian to write content. The outlining experience is phenomenal, but the writing experience is frustrating. I’ve followed everything in the Making Obsidian play nice with Logseq guide, but the experience is still not great.
The format that Logseq generates is mostly compatible with Obsidian. Since the beta release, Logseq uses “standard - unordered list as outliner bullets”. This was a nice compatibility enhancement, but I still have some major gripes.
(These examples are snippets from my personal notes. I write meeting notes, notes on dog training techniques, and catalog recipes and meals that I have. Please ignore the content if you can help it )
Block references are not compatible.
Block references written in Logseq rendered in obsidian:
Block references written in Obsidian and rendered in Logseq:
I don’t know if this is something that will ever be compatible just because of how different Logseq and Obsidian implement their Block references; Logseq uses a UUID attached to a Block Property to identify a block, and obsidian uses a more standard [^uniquehash] markdown footnote-style reference.
Hi thank you for making this post! I recently also tried to make these two working together but failed : (. I think right now the most difficult thing is the block reference (which I unfortunately used a lot) since these are two totally different implementation
Yes, the as-yet untranslatability of block references is indeed a major pain point. I have decided for the moment to keep block references for Logseq use only, as Obsidian block references makes considerable chaos in Logseq by creating meaningless pages.
It is possible, however, to navigate Logseq block references in Obsidian without too much difficulty. For example, one can simply search for the reference ID. Not ideal but it works well. I’m also aware of a script for Obsidian that makes that process even easier (created by a user of Obsidian). Hopefully I’ll be able to share it soon.
I see a lot of featurerequests for Logseqto emulate someObsidian feature. I get that these products are similar, but they are also different. I like that Obsidian appears to be built atop a plugin architecture where everything, even the core, is a plugin. I like that because it means I can opt out of a lot of cruft I don’t want (e.g. Zotero) but which is integrated into Logseq by default.
Other than that, I don’t like the idea of Logseq becoming more like Obsidian. I like the Logseq user experience better than Obsidian, at this point. So the notion of Logseq doing Obsidian is lost on me.
Now if the Obsidian must-haves are nothing more than plugins, that’s great because that doesn’t impose one person’s view (Obsidian does X better) on the whole community. And if Logseq makes plugins a centerpiece to its design then lots of Obsidian-like things can be supported via plugins.
As far as collaboration goes, I am sure Obsidian and Logseq are cross pollinating but I see no way around having to rewrite features/plugins for both. Basically, all this request amounts to is configurability. Let users choose what things to configure to be more like Obsidian and, with plugins, that’s possible.
I wonder if Logseq could switch to a more common and user-friendly format for callouts, aka admonitions.
Obsidian has chosen to follow the syntax created by Microsoft. Github (owned by Microsoft lol) has gone somewhat different.
But all use a modified Blockquote, which I believe was chosen so that it renders decently in markdown processors that don’t understand callouts.
It would be great of Logseq moved away from the org-mode style #+BEGIN (which I’ve always found difficult to remember and type in my org-mode days, even before the better ``` syntax was invented)