Repository navigation
Releases
FrankMDFast 0.1.2
FrankMDFast 0.1.2 makes ⌘ shortcuts work across the app on macOS.
Fixed
- macOS: every shortcut now answers to ⌘ as well as Ctrl — ⌘P, ⌘S, ⌘B, ⌘⇧P, ⌘W, … — contributed
by @Okaada (#5). Ctrl keeps working everywhere and Linux/Windows behavior is unchanged. - macOS: the media and grammar dialogs accept ⌘↵ and ⌘1–⌘7; the delete-confirmation dialog accepts
⌘↵ and the explorer's select-all accepts ⌘A. - Shortcut labels (command palette, help, status-bar chip, empty-state hints, dialog buttons) now
derive from one table and print ⌘⇧P style on macOS; the note switcher shows ⌃Tab because ⌘Tab
belongs to the macOS app switcher. - The macOS app menu's key equivalents show ⌘ (for example ⌘Q) instead of ⌃.
Downloads
| System | File |
|---|---|
| Linux x86_64 / aarch64 | FrankMDFast-0.1.2-<arch>.AppImage or frankmdfast-0.1.2-linux-<arch>.tar.gz |
| Arch Linux | yay -S frankmdfast-bin |
| macOS (Apple Silicon and Intel) | FrankMDFast-0.1.2-macos-universal.dmg (signed and notarized) |
| Windows x86_64 | FrankMDFast-0.1.2-windows-x86_64-setup.exe or the portable zip |
FrankMDFast 0.1.1
FrankMDFast 0.1.1 fixes note and folder creation on Windows and the basic macOS window
behavior reported against 0.1.0.
Fixed
- Windows: creating notes and folders works again (#1). Vault operations joined paths with
/
onto the canonicalized notes root, which Windows reports as a verbatim\\?\path; verbatim
paths reject/, so every create, open, save, rename and delete failed with the generic
"Failed to create". Paths are joined with\there now, and the Windows CI job runs the note
and folder flow on a real filesystem so it cannot return silently. - Windows and Linux with client-side decorations: the window has a title bar with close,
minimize and maximize buttons and a drag area, instead of no controls at all. - macOS: the sidebar header no longer sits underneath the traffic-light buttons (#2).
- macOS: clicking the Dock, Launchpad or Finder icon after closing the window with the red
button reopens the window instead of doing nothing while the process keeps running (#3). - macOS: ⌘Q quits the app, through a proper app menu; the shortcut help that showed ⌘Q now
matches the key that actually works (#4).
Downloads
| System | File |
|---|---|
| Linux x86_64 / aarch64 | FrankMDFast-0.1.1-<arch>.AppImage or frankmdfast-0.1.1-linux-<arch>.tar.gz |
| Arch Linux | yay -S frankmdfast-bin |
| macOS (Apple Silicon and Intel) | FrankMDFast-0.1.1-macos-universal.dmg (signed and notarized) |
| Windows x86_64 | FrankMDFast-0.1.1-windows-x86_64-setup.exe or the portable zip |
FrankMDFast 0.1.0
First release of FrankMDFast, FrankMD as a native desktop app, rewritten in Rust with GPUI.
It is a drop-in replacement for the Rails FrankMD: it reads the same .fed file and environment
variables and works on the same folder of notes, so you can switch between the two.
Highlights
- Markdown editor with live preview, math, syntax highlighting, tables, tasks and wikilinks
- Vim mode, typewriter mode, find and replace, command palette (Ctrl+Shift+P) and quick open (Ctrl+P)
- Hugo blog posts, image and video embedding (local folder or S3), YouTube and image search
- AI grammar check and image generation with OpenAI, Anthropic, Gemini, OpenRouter or Ollama
- Follows the Omarchy theme and language live; 18 built-in themes
- Settings for every option, including interface size (80–200%)
Security changes compared with FrankMD
- Uploads must really be images or videos (content is checked, not just the extension)
- URLs with
user:password@are refused - The AI grammar check never sends
.fedor secrets - Search, backlinks and media scans never follow links out of the notes folder
Downloads
| System | File |
|---|---|
| Linux x86_64 / aarch64 | FrankMDFast-0.1.0-<arch>.AppImage or frankmdfast-0.1.0-linux-<arch>.tar.gz |
| Arch Linux | yay -S frankmdfast-bin |
| macOS (Apple Silicon and Intel) | FrankMDFast-0.1.0-macos-universal.dmg (signed and notarized) |
| Windows x86_64 | FrankMDFast-0.1.0-windows-x86_64-setup.exe or the portable zip |
The Windows build is not code-signed yet, so SmartScreen will ask before the first run.
Check downloads against SHA256SUMS.
Known gaps
Relative line numbers, right-to-left layout for Hebrew, settings "Test connection" buttons and a
keyring for secrets are not done yet. On Windows a second launch opens a new window instead of
reusing the running app.