obsidian-git VS pandoc

In practice I write in Obsidian, the best thing since slice bread for me. And it was obsidian-git, running every 10 minutes or so, who was keeping my GitHub vanity metrics very green.

> Joplin is using md to.

The way it's handled can make the difference in control.

> by separating that in their DB, it's a big NO for me since it's a closed silo.

Joplin is using a popular open database with a healthy community and good tooling. It's as open as markdown. Maybe not for you, when you lack the knowledge, but markdown is similar closed for anyone not understanding filesystems and editors.

> This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me

Good for you, but that is very low level in terms of data-handling. Dataview is really just an elaborated search, there is no good level of interaction. Datacore, the next project of the Dataview is supposed to bring this, but it's not even usable yet AFAIK. Coincidental, the Obsidian-devs are also working on that front, but nothing is finished yet.

> https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!

That's useless when the app itself is not working. And even worse if you are not realizing the errors early.

> Aha. I don't think so. Which authority says that?

My own experience. I've tested enough plugins over the years to know their dark corners.

> And even if It's like that, my markdown files would survive everything

The thing is, technically you are not even having proper markdown, but a fork with some extensions of Obsidian. So some features of your parts might break when switching away from Obsidian. And the reason for all this is also because markdown is lacking definitions for what obsidian-people are doing with it. Coincidentally, this seems also one of the reasons why Joplin is using a database.

> And gosh, this is a good thing!

Not if they all suck.

> Installing multiple task plugins shows that something is "broke" on the user side.

Sure, because the plugins are lacking features, its the users fault... Maybe some users have just very different levels of requirements from you.

The Obsidian team uses the "remote vault" feature[1] to collaborate on making Obsidian. Since Obsidian runs on local files you could use any shared file storage like Dropbox. If you want more granular version history, you can use Git, there's a nice plugin for it[2].

[1]: https://help.obsidian.md/Obsidian+Sync/Share+remote+vaults

[2]: https://github.com/denolehov/obsidian-git

I've been using the main Obsidian git extension, https://github.com/denolehov/obsidian-git. Took some work to set it up ergnonomically but it works great now. I enabled auto-commit and push on save, and auto-pull when you start the editor. No merge conflicts yet between two machines.

Should note I use Obsidian for a journal, so it's pretty much append-only.

I use Obsidian to create notes as Markdown files on my computer and use the Obsidian Git plugin to version control the changes via Git. The Obsidian vault in which I store my notes is stored in a folder synced using iCloud Drive.

Up to my knowledge, Obsidian GIT doesn't support merge on mobile. There is a different approach for handling those on mobile using Command Line, you can find more info in this post and this article.

Plugin: https://github.com/denolehov/obsidian-git

I am using Git for that. Here is the extension that might help. https://github.com/denolehov/obsidian-git

My main authoring tool is then Emacs Markdown Mode (https://jblevins.org/projects/markdown-mode/). For data entry, it comes with some bells and whistles similar to org-mode, like C-c C-l for inserting links etc.

I seldom export my notes for external usage, but if it is the case, I use lowdown (https://kristaps.bsd.lv/lowdown/) which also comes with some nice output targets (among the more unusual are Groff and Terminal). Of cource pandoc (https://pandoc.org/) does a very good job here, too.

This is one of those things that the ever-amazing pandoc (https://pandoc.org/) does very well, on top of supporting virtually every other document format.

Folks feel the same way about Markdown versus LaTeX: why use something significantly more complicated where a looser, human-readable grammar works better?

For any other situations, I use https://pandoc.org/, or, generate a Word doc scriptomatically.

pandoc toolchain pour builder une version confortable/imprimable en phase de travail (ePub, pdf, docx, html)

Congrats on the launch, I guess, but there are so many free options that I can't think of a situation where paying $0.25 per document would be justified...? Just to name a few:

Back in the days, I used to use XSL-FO [0] and it was okay. It was not very precise but it rarely if ever broke, and was perfectly integrated with an XML/XSLT solution. Yeah, this was a long time ago.

Last month I used html-to-pdfmake [1] and it's also not very precise and more fragile, but very efficient and fast.

Yet another approach would be to pro grammatically generate .rtf files (for example) and use Pandoc [2] to produce PDFs (I have not tried this in production but don't see why it wouldn't work).

[0] https://en.wikipedia.org/wiki/XSL_Formatting_Objects

[1] https://www.npmjs.com/package/html-to-pdfmake

[2] https://pandoc.org/

Others have mentioned static site generators. I like Hakyll [1] because it can tightly integrate with Pandoc [2] and allows you to develop custom solutions if your needs ever grow.

[1]: https://jaspervdj.be/hakyll/

[2]: https://pandoc.org/

Have you compared it with a conversion by pandoc (https://pandoc.org/)?

I have used it to kickstart a blogging project that I wish to come back to soon. The Lua inter-op for custom readers, writers and filters is great but I wish there was more editor integration and even perhaps an official IDE/editor with built-in debugging features (probably something already do-able with Emacs but I haven't checked). The only blocker for my project is no support for "ChunkedDoc" for Lua filters [1] which forces me to write more code and a complicated Makefile.

[1]: https://github.com/jgm/pandoc/issues/9061