101–110 of 157 posts
My use case is keeping notes, screenshots sometimes, whatever in the same format sometimes...
Wouldn't you feel limited by the markdown. What is the use case?
I tried it and it looks really nice but like most of these it has too many small editing thorns for me to use. Two I noticed right away - ctrl-a works to go to start of line but for some reason ctrl-e doesn't work to go to end - ``` doesn't start a code block, you have to use 'insert code block' Good job on paste image from clipboard though which is another feature that I think is completely essential for something l…
``` should definitely start a code block! I do it all the time, and also just tried it now. Can you try again or tell me what you see? Simply nothing happening?
```[ENTER]
and
```python[ENTER]
and I also assumed there was no code highlighting but I see after I add a code block I can select the language through the UI
```[SPACE] works, but immediately places the cursor below the block where I'm more used to the cursor moving into the block after creation
Why would I want to join a club where I, as a human, would be a second-class citizen?
Earlier quoted context omitted.
I started Tolaria in Swift but met very real limitations especially in the Markdown editor part. It's very hard to build something that is Notion like in that department with Swift. But give it a try because Tauri is very fast
At least for me it’s not about speed, but the npm ecosystem: I try to avoid running npm deps in my home computer (if any, I run them in VMs, but a KB should run in the host I believe)
It seemed like a nice thing at first glance, but I was quite put off to see "AI-first but not AI-only". Why would I want to join a club where I, as a human, would be a second-class citizen?
Earlier quoted context omitted.
Obsidian and these newer tools share markdown + local files, but they're aimed at different assumptions about who reads and edits the vault. Obsidian's default is "human reads and curates; plugins optionally enhance." The AI-first cohort (Tolaria, Sig in the sibling comment, and several others) assumes the AI reads and writes as a first-class agent, which makes design choices like how the app reacts to files changing…
It would be nice if you could “see” the AI in your vault making changes. Almost like a Google doc collab session. Even if you weren’t directly interacting with the agent, and it was making change thru a CLI/MCP, its presence would be highlighted in the frontend. And then it appears as its own contributor in the git history.
I've been working on this split in a side project (https://github.com/rillmd/rill — vault layer on top of Claude Code). Git still handles the durable side for free, since the CLI agent just writes files and commits normally. The live side comes from Claude Code hooks (UserPromptSubmit / Stop / PostToolUse) appending to a plain activity-log.md that the Electron GUI tails. Cruder than Google Docs cursor presence, but cheap — and the log itself is just another markdown file in the vault, same data model as everything else.
One trade-off: going the other direction and letting the frontend detect edits via FSEvents-style watching runs straight into the reconciliation issues the Zettlr subthread is about. Hooks on the agent side are less elegant but sidestep the whole class.