I can relate. However, I’m using Linux (Void Linux) as my daily driver.
For me, the outliner functionality is the primary attraction to Logseq for me. Obsidian has a few plugins that approximate what Logseq does.
Since Logseq is developing a Database version, I am looking at alternatives.
SilverBullet (SilverBullet) is at the top of my list. I’m going to play with it and see what I can do with it.
SilverBullet is awesome! Very smooth. The developers added a Vim mode just days after I requested it last year. My only caution is I’ve had some strange sync local/remote sync issues since the local webpage caches the files you load that are really stored on the server - but could have been resolved.
Curious if it has any of the outliner features or is missing anything you want, though.
1 Like
The DB version of Logseq will still have all the same outliner functionality as the current version.
From time to time I wonder about trying to use Logseq as a simplistic .md outline editor on single files that are otherwise managed by Obsidian… Or, like having a Logseq-specific folder in the Obsidian vault. I wonder how much undesirable stuff would Logseq drop around. I need to test it.
And just recently I learnt that Obsidian’s devs are also the developers of Dynalist! I’m afraid that that means that if they wanted to make Obsidian a GOOD outliner they would have done so long ago 
2 Likes
Dario Da Silva has been using both Logseq and Obsidian on the same folder/vault for some time now. Check out his YouTube channel @combiningMindspkm.
Ahhh…that is why I am playing with it now while I still have time.
I can always shift to something else. It looks like it will be a while before the new logseq will be fully implemented. Besides, my concerns may end up being mute. Who knows?
Interesting, will check it. Thank you!
EDIT: found a couple of his videos, and well, when a productivity guru tells me to pop out VSCode to fix properties, I’m reminded that a lot of this is unnecessary procrastinating madness.
I just explored migrating to Obsidian (struggling with Logseq’s limited sync and search functionality), but the only way to use Obsidian as an outliner using keyboard shortcuts is with the Outliner plugin, which is extremely strict in its formatting requirements and doesn’t seem to have a way to highlight or auto-correct problems. (see this open issue on the plugin page)
I finally concluded that it would take too much effort to patch up all of my pages for Outliner to accept them.
I use Logseq for outlining and Obsidian for long-form. My daily journal and brainstorming is in Logseq. Depending on your settings, both can use the same graph or vault. I use GitHub to sync.
How to setup sync like this?
There is no sync to set up. Have Obsidian open your Logseq folder as a vault. There are several behavioral changes (or formatting elements) to remember.
If you use task management in Logseq, the formatting is entirely different. That might take time to convert; however, you can keep using Logseq.
Both note-taking applications have strong points. They can help in different areas, such as research, writing, or time management workflow. Because everything is still markdown, the most significant value is workflow.
For some time now, I’ve been helping clients with document management. The most important thing is always the deliverable or outcome you desire.
Because both tools can read the same file set, you can switch between the two despite a few formatting differences. No syncing required.
I use Typora for longform. The use of Obsidian and the necessary system building besides the one you have to maintain also in Logseq would be “too much.” Logseq as the main until there is a need for a longform node, based on a markdown syntax.
Are you saying Logseq doesn’t rewrite your long form in the same repository if you use Typora as a markdown editor?
My use case is brainstorming, idea capture, organizing outlines, and developing ideas in Logseq. Like a stack of index cards. Then, I will compose those notes in Obsidian before publishing them via Zettlr or Scrivener.
The extra work is making sure configurations between Logdeq and Obsidian are cooperative. The whole vault is in GitHub. Beyond that a little backend formatting has been my biggest frustration.
I use Typora for longform writing precisely because it simplifies the workflow. While your approach with Obsidian makes sense, maintaining two complex systems (Logseq and Obsidian) alongside their configurations feels redundant when Typora can handle the longform needs with less overhead. I keep Logseq as my main knowledge hub - for brainstorming, outlining, and developing ideas - but when it’s time to compose longer pieces, I just open the markdown files directly in Typora. This gives me a clean, focused writing environment while keeping everything in the same repository structure, avoiding the extra complexity of syncing and maintaining configurations between Logseq and Obsidian.
The beauty of this setup is that both Logseq and Typora respect the underlying markdown format, so there’s no need for complex conversions or worrying about formatting inconsistencies. When I need to write something substantial, I can seamlessly transition from Logseq’s structured thinking environment to Typora’s distraction-free writing space. It’s a more streamlined approach that lets each tool do what it does best without the additional system building that comes with incorporating Obsidian into the workflow.
1 Like