org-journal VS obsidian-git

I use org-mode with org-journal https://github.com/bastibe/org-journal

What's nice about this workflow is when I create TODO items and don't finish them for a day it transfers over to the next day.

Sounds like org-mode is what you need, particularly clocking like was mentioned in another comment. However your workflow requires lots of customization. Ultimately you need to take a deeper dive into org-mode and what it can do(and how), along with org-clock-convenience with maybe org-journal. Your starting point should always be agenda, not the .org file itself.

As mentioned elsewhere, I too do a mix (happy to talk fountain pens and paper if you’d like). But for digital, Emacs is the supreme solution. It has tools like Org-roam for Zettlekasten-style notes, Org-journal for a developers journal, Org-babel for literate (or Jupyter-style) explorations. Nothing else comes close. Oh, and the “E” stands for extensible, so if it doesn’t do what you need, you can make it yourself.

For the second question, 1. try package like org-reverse-datetree and org-journal which can custom data format and level. 2. use file+function in capture template to find the right location in the file. 3. make the function in 2 respect you extend-day-until.

org-journal seems to fit your description pretty well. I have been using it for years.

- type my timestamped notes

I can do this from any buffer in Emacs, so it's really convenient to stop in the middle of something, jot down a note, and then go right back to what I was doing. I develop iOS/macOS software right now, so the switch to Emacs from Xcode is a little more friction than I used to have, but it's so useful I don't mind it at all.

I have a weekly journal in a directory for the year, titled week number-month-day that started that week (this week's is `34_08-23`)

[0]https://github.com/bastibe/org-journal

bastibe/org-journal is already a feature full extension to Org for keeping a journal. And actively maintained by Bastian and Christian.

I'm interested in using org-journal, a minor mode for Emacs org-mode, which supports collapsing. https://github.com/bastibe/org-journal

    * Tuesday, 06/04/13

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