2 ms·
> Obsidian's response to users' complaints about this was not reassuring This is my main worry about choosing Obsidian for the long run. The devs seem very opi
by muwtyhg 3y ago
> Obsidian's response to users' complaints about this was not reassuring
This is my main worry about choosing Obsidian for the long run. The devs seem very opinionated about a system that is meant to be customizable to each user's workflow.
Their Vim implementation does not support setting hard line breaks, making modal editing a little funky (every paragraph is just one long line and any action working on a line will work on the entire paragraph, such as "dd").
Came from Vim-Wiki (and Org-mode and some other short-lived note-taking systems) and I think the plugin hell of Vim/Emacs (or VS Code) is much worse than Obsidian. You can get by without any addons in Obsidian as it's built to be a notetaking system first, not a general text editor. You can't do the same with Vim (hence needing "Vim-Wiki" plugin).
- rchaud 3y agoI've also noticed that Obsidian hides text automatically inside of <div> or other HTML elements if they contain the property "markdown='1'", thereby blocking you from writing perfectly valid HTML inside of a Markdown file which was designed to be HTML-compatible.
- pcthrowaway 3y agoIs the markdown=1 attribute part of the HTML spec? I can't find any indication that it is.
- echoangle 3y agoAttributes dont need to be in the spec, if I add an attribute mycustomattr="xyz" and it changes how the document is rendered, that probably violates the HTML spec.