Posted by shibaobun 2 days ago
+ It’s all within the editor you already know really well. Uses your existing tools.
+ Many editors have really good support for markdown built in. Treat H1’s like notes and along with modern fuzzy search for files/symbols you can easily get to any note and jump around.
+ If you want smarter [[liking]] there’s some good plugins out there to bring this to your editor.
+ Simple, future proof and no lock-in.
I’m currently enjoying markdown-oxide, an LSP for markdown docs. Captures all your notes as symbols so you can fuzzy search and “find references”, etc. supports #tags, too.
Mermaid: Diagramming and charting tool: JavaScript based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.
Include diagrams in your Markdown files with Mermaid: A picture tells a thousand words. Now you can quickly create and edit diagrams in markdown using words with Mermaid support in your Markdown files.
https://github.blog/developer-skills/github/include-diagrams...
Creating diagrams: Create diagrams to convey information through charts and graphs:
https://docs.github.com/en/get-started/writing-on-github/wor...
The Official Guide to Mermaid.js:
https://github.com/PacktPublishing/The-Official-Guide-to-Mer...
```mermaid
```
My obd vault is "a folder of markdown docs" (which retains the "future-proof, no lock-in" benefits you cited). But the excellent WYSIWYG UX (open files in Edit mode, w/ "Live Preview" enabled) is something I haven't seen replicated in any VSCode or Cursor extension/plugin. I also prefer a dedicated tool for note-taking and "PKM" (Personal Knowledge Management"), as a peer of my IDE(s) for coding. I get to use the best tool for the job, w/ no compromises. Switching to a different IDE for a given project (eg IntelliJ for wrangling Kotlin) doesn't disrupt my workflow, and having clear context boundaries (note-taking vs coding) is a personal preference.
YMMV, different strokes,.... I know some emacs org-mode fans out there will extoll the benefits of using "one tool to rule them all", which does sound compelling... (shrug).
I love that there are such a variety of quality tools and approaches -- and, I'm very happy with mine.
I think what matters more is like you say - how the data is stored. It's been nice to see this convergence towards markdown and it's this that's seems the real sweet spot (or plain text, more generally). Separate the data from the logic and you're free to operate on your notes with whatever fits at the time, or even with different tools at the same time (on mobile, say).
Not news to many folk here on HN but a refreshing contrast to other PKM that use proprietary formats, often along with monthly subscription fees for what is essentially variations on "editing a plain-text database".
Eventually I moved to using vscode for both. My gigantic notes.md file is always open in tab 1, so I can go to it immediately with Ctrl + 1.
Finding notes in a single file is easier for me than finding them in a bazillion tiny files. And there's less friction whenever I need to make a note (no need to create and name a new file).
Keeping everything in a git repo makes it easy to sync across devices + backed up.
Works pretty well so far with some acceptable nitpicks. It was a quick and dirty solution to overcome logseq couldn't run in a Server that time... Never needed anything else until now :-)
Tried to figure it out a few months ago and it seems like they just disappeared.
(From Protesilaos, whose introduction to emacs was also on the front page at the time of writing this comment)
I bought “How To Write Smart Notes”, but it’s misnamed: it should've been “Why To…”. I hoped it would tell me how to use Zettelkasten, but by the end it seemed to be a long sales manual without a how-to guide.
I wrote code to facilitate the migration. Nothing too crazy, but in general I wrote scripts that:
- Add lines between logseq's daily notes format and the rest of the content
- Moving daily notes to month-based subfolders
- Automatically adding frontmatter to files that didn't have any
- Removing indentation when unnecessary
- Covert everything to space-based indentation rather than tabsI definitely have a preference for outliner, flat zk style, but I'm able to get the majority of the benefit from Obsidian while having access to a stronger ecosystem of plugins and first class publishing and syncing support. Meanwhile Logseq seems to have lost a lot of steam.
[1] https://memex.bubbletea.dev/pipeline/evaluate-life
[2] https://misskey.bubbletea.dev/files/73e9088a-a696-45de-9f17-...