Letting ideas flow into your next presentation, paper or book.
Markdown meets the power of LaTeX in this modern typesetting system.
Letting ideas flow into your next presentation, paper or book.
Markdown meets the power of LaTeX in this modern typesetting system.
Thanks for sharing, looks really cool! Especially with how prevalent markdown is.
Hopefully this isn’t too off topic/thread derailing:
As a longtime LaTeX enjoyer, lately I’ve become increasingly infatuated by Typst. With Excalidraw quickly winning my favour as well …
However I find myself daydreaming of some of Obsidian’s powerfull features for knowledge graphing/“second brain”-ing, but given various reasons, never successfully convinced myself to use it. (Primarily: markdown seemingly a bit too simplistic for my preference, and Obsidian, to my knowledge, not being open source(?))
Instead I’ve tried some alternatives, each with excellent ideas, unfortunately none really hitting home with my wierd brain.
e.g. Zim, LogSeq, SiYuan, ...As such I’m curious to hear about others’ setup, and thoughts. - Is Some(Quarkdown + Obsidian) perhaps what I’ve truly been longing for for?
Have you tried org-mode in emacs? It’s got everything and more! You have zettelkast-style note taking, journal, agenda, spreadsheets and a bunch of other stuff. And everything is saved in text files.
Emacs really is a great operating system!
Perhaps it is time I delved into the world of Emacs. I’ll check org-mode out, thanks :)
FWIW, I was hesitant about obsidian for the same reasons. I would’ve preferred an open source editor and a syntax like asciidoc. But the fact that everything is markdown and it being such a common standard does make obsidian being closed source more palatable[1]. And tbh, for note-taking/“second brain” purposes, a relatively constrained format like markdown is pretty suitable. I wouldn’t want it for technical writing but it serves the purpose for quick and dirty tasks like quickly jotting down notes[2]. And any other markdown language wouldn’t have the same amount of tooling (e.g. org-mode is underspecified and essentially emacs-only unless you see stick to a specific subset of features)
see the creator’s blog post: “File Over App” ↩︎
in an ideal world a more sane/context-free syntax like Djot would have been nice ↩︎
Trillium Notes Next is a good open-source obsidian alternative without the bullet points of logseq.
I did use the previous one. Liked it well enough, despite having some config issues. (definitely my own fault though)
But then it entered maintenance mode, and I had a few alternatives to try out … It’s good to see it lives on though, so I’ll keep an eye on it as I might give it another go, thanks :)
It’s definitely worth keeping an eye on. Keep in mind that the name of the fork currently under active development, TrilliumNext Notes, will soon change to just Trillium Notes, like the original software it was forked from, according to the release notes of the latest version (0.94.1).
As a Typst enjoyer I have to say this isn’t it imo from a quick look at the readme. Typst’s mix of markup and code modes is excellently designed and a high bar for anything to beat, and this looks like it doesn’t come remotely close. (I do have to say, I also heavily dislike Markdown in general)
Well, Typst is explicitly a no-go for anyone who has to submit a manuscript, until it they get a damn HTML representation, so Pandoc can get it to LaTeX. There’s practically nowhere I could use Typst except my own notes, and I’ve tried!
There’s experimental HTML support. I’m using Typst as a static site builder for my website.
Sure, but they can’t build Pandoc translation against an experimental format, so no LaTeX anytime soon.
The experimental status is more about that not everything is implemented yet (not that everything can be implemented, for example due to HTML not being oriented around having multiple pages in a document), so you have to write a bit of raw HTML sometimes. This is an example of how raw HTML looks, it’s the shell for my webpage.
Looking through some of the docs I’m afraid I won’t be able to move off of Typst to this either. Typst has a long standing bug that I would have liked to avoid (lists that are too long will overflow memory and the maintainers seem to not want to temporarily dump to disk) but if even rust has an issue with those 100k+ row lists, I’m not sure kotlin will handle it better.
Lists with 100k items? Impressive. I can see how with a document like that it will run out of memory. Is it a stack overflow? You could try increasing the stack size in that case.
Did you try Silverbullet? I tried a lot of the stuff you mentioned, but aside from the poor documentation, this hits the sweet spot between power use and carefree for me.
Looks interesting, I’ll have to dig a bit deeper into it! Thanks for sharing :)