Fork logseq to make alternative org-roam frontend

Development
1

Logseq is great and already compatible with org-roam in many ways(displaying highlight, the outliner structure (to some extent), id-link).

However there’s still a list of stuff that are markdown-faced hardcoded, unconfigurable for end user:

  • file creation template
  • code block is hardcoded to ``````, the markdown syntax
  • link created and worked in logseq remain [[title]] and not id-link (so don’t work in emacs, and logseq-org-roam don’t treat them for me)

Personally, my use case is the whiteboard, and I find it quite irritating that I cannot create new note in whiteboard due to the above issues. So I’m thinking of making a logseq fork that exposes the above mentioned logic for configuration, and probably some other nudge here and there (like that super long headline without body logseq makes, or that dysfunctional template system) to make a more org-roam-facing front end.

Any thought on that or have anyone already done that? I’ll probably start in a week. (hands are tied on other project right now)

2

on another note, I’m also thinking of writing some portable frontend for org-roam including that whiteboard feature in CLOG in the near future.

In my mind REPL to the cl runtime can be exposed there and we can have a pretty emacs-like experience in there with user functions and global customizability. (It might not work too well :wink: I’ve used nyxt)

I’m unaware if logseq can expose the cljs runtime already. I remembered that although it is possible, its not a common practice in “production release”. I’m also unaware how much cljs’s repl can do, as if I’m not mistaken cljs compiles to js, and I assume once that happened with clozure compiler or something they would escape the control of cljs repl.

3

The repo I’m gonna do it in: Hermanhel/lorgseq: an org-roam facing fork of logseq https://github.com/logseq/logseq - Forgejo: Beyond coding. We Forge.

1 Like