Outliner Software Forum RSS Feed Forum Posts Feed

Subscribe by Email

CRIMP Defined

 

Tip Jar

Logseq + Obsidian

< Next Topic | Back to topic list | Previous Topic >

Pages:  1 2 3 > 

Posted by Luhmann
Jun 11, 2021 at 02:34 PM

 

This has been discussed elsewhere, but I felt it deserved its own thread.

Logseq is a Roam clone that stores its data as plain text files which are mostly markdown as well as some extra parameters, such as text to tell the app whether each part of the outline is open or collapsed. Lately Logseq released a desktop app that lets you save the markdown files in a folder of your choice. This means that you can open those same files in Obsidian and work on them from there as well. An added advantage of this is that you can then use the Obsidian mobile app to access and edit your Logseq files. Some of this is still a bit rough, but development is fast and it now seems to me that it is stable enough to start working with. I’m not (yet) ready to jump from Roam, but I spent some time setting everything up so I can continue to use it in parallel to my main Roam database.

To get Obsidian to play nice with Logseq there are some settings you need to change. It took me a while to figure it all out, so I thought I’d share those instructions here in case anyone else wants to give it a try. Some of this is because Logseq has its own dedicated folders for storing files and attachments, others because of how logseq handles daily journals, and also some to handle the unique way Logseq handles tasks (which is actually pretty nice):

# managing pages

- Files and Links > default location for new notes > in the folder specified below > “pages”

# managing attachments

- Files and Links > default location for new attachments > in the folder specified below > “assets”

- Files and Links > new link format > relative path to file

- Files and Links > Use Wikilinks > off

# Journal Daily notes

- Core Plugin > Daily Notes > On

- Daily Notes > date format > “YYYY_MM_DD”

- Daily Notes > new file location > “journals”

# Tasks

- Create a page called [[logseq tasks]]

- create queries on that page in the form:
    - `match-case:DOING`

# outlining

- Install “Outliner” and “Zoom” community plugins

 


Posted by Luhmann
Jun 11, 2021 at 02:35 PM

 

Link to the logseq desktop beta:

https://github.com/logseq/logseq/releases

Link to Obsidian:

https://obsidian.md/

 


Posted by Alexander Deliyannis
Jun 11, 2021 at 03:35 PM

 

Wonderful! Thanks so much for sharing!

Luhmann wrote:
>To get Obsidian to play nice with Logseq there are some settings you
>need to change. It took me a while to figure it all out, so I thought
>I’d share those instructions here in case anyone else wants to give it a
>try.

 


Posted by Christoph
Jun 11, 2021 at 05:23 PM

 

Didn’t try it myself, but did you see this?

“Obsidian and Logseq - Why Use Both?” - https://www.youtube.com/watch?v=WpnbSWt_mgM

 


Posted by Luhmann
Jun 11, 2021 at 11:47 PM

 

My own thoughts about why this is so amazing:

1. All files are stored in plain text markdown files on your local computer, not in a database.

2. No “loading” screen when you start - works instantly.

3. Mobile support that is pretty full featured, since the Obsidian mobile app is excellent.

4. Access to the Obsidian community plugin library and developer community which is pretty good, better in some ways than Roam’s.

5. But still have a Roam/Workflowy/Dynalist like outliner interface when you want it via Logseq.

Put another way: Obsidian is in many ways superior to Roam (see the above reasons 1-4), but suffers from lacking a WYSIWYG interface or a Dyanlist-quality outlining interface. Logseq basically gives you those things but you can still use Obsidian when you need some Obsidian unique features, such as a mobile app, Readwise import, etc.

 


Pages:  1 2 3 > 

Back to topic list