File sync between raw Markdown and the editor #1
Description
Summary
Philo should stay in sync with the raw Markdown file on disk, both ways. Right now, edits made outside the app (e.g. in Zed or Obsidian) aren't picked up, and changes made inside the app don't always faithfully reflect back to the file.
Expected behavior
External edits → App
- When a Markdown file is edited in an external editor (Zed, Obsidian, etc.), the app should detect the change and update the editor view in real time (or on focus/re-open at minimum).
- Formatting must be respected as-is. For example, two consecutive empty lines in the file should render as two empty lines in the app — not collapsed or stripped.
App edits → File
- Every change made inside Philo (typing, creating a new line, deleting, etc.) must be written back to the raw Markdown file immediately and accurately.
- The file on disk should always be a faithful representation of what's in the editor.
Why this matters
Users who keep their notes in plain Markdown expect their editor and their file system to stay in sync. Philo acting as a walled garden breaks workflows that span multiple tools.