A high-performance data index and query language over Markdown files, for. A plugin for Obsidian that helps you write and edit novels, screenplays, and other long projects. When comparing fsnotes and obsidian-git you can also consider the following projects: "fatal: bad object refs/heads" and "conflicting files".Need some help: Obsidian/Obsidian Git can't sync/push to remote.Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser and nvim Just have a look on: but you dont need a fancy task plugin like this, if you know your way around or It's not the fault of Markdown or Obsidian. Installing multiple task plugins shows that something is "broke" on the user side. > At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates. > And gosh, Obsidian has really a huge amount of plugins for data-handling. and b) easy to fix since it's a text file. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. > Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.Īha. This: works so wonderful for me, and it never breaks anything in my simple md files. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo. > Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content. Obsidian has its shares of problems too, and most of them originate from using Markdown. Maybe some users have just very different levels of requirements from you. Sure, because the plugins are lacking features, its the users fault. > Installing multiple task plugins shows that something is "broke" on the user side. Coincidentally, this seems also one of the reasons why Joplin is using a database. And the reason for all this is also because markdown is lacking definitions for what obsidian-people are doing with it. So some features of your parts might break when switching away from Obsidian. The thing is, technically you are not even having proper markdown, but a fork with some extensions of Obsidian. > And even if It's like that, my markdown files would survive everything I've tested enough plugins over the years to know their dark corners. And even worse if you are not realizing the errors early. That's useless when the app itself is not working. > and b) easy to fix since it's a text file. Coincidental, the Obsidian-devs are also working on that front, but nothing is finished yet. Datacore, the next project of the Dataview is supposed to bring this, but it's not even usable yet AFAIK. Dataview is really just an elaborated search, there is no good level of interaction. Good for you, but that is very low level in terms of data-handling. Maybe not for you, when you lack the knowledge, but markdown is similar closed for anyone not understanding filesystems and editors. Joplin is using a popular open database with a healthy community and good tooling. > by separating that in their DB, it's a big NO for me since it's a closed silo. The way it's handled can make the difference in control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |