Known issues.

What you see

You double-click Markify and nothing happens: no window, no error, no crash report, and Markify doesn’t appear in Activity Monitor. Only its Quick Look extension (MarkifyQuickLook) runs. Reinstalling doesn’t help.

What happened

Version 2.0.0 added the markify command-line tool. When the release was packaged, the tool was copied to Contents/MacOS/markify, next to the app’s own program Contents/MacOS/Markify. On a Mac’s default, case-insensitive disk those are the same file, so the command-line tool replaced the app. Opening Markify ran the tool, which printed its help text and quit.

The bug was in the release packaging only: Gatekeeper, your settings and how you installed Markify had nothing to do with it. Builds made in Xcode were never affected, which is why it slipped through.

Versions

How to fix it

Markify can’t update itself from 2.0.0 or 2.0.1, because it never starts. Install 2.0.2 by hand; your documents and settings are kept.

1. Download Markify 2.0.2 from the release page or the download section: markify-as.dmg for Apple silicon, markify-intel.dmg for Intel.
2. Drag Markify to Applications and choose Replace.
3. Open Markify. On 1.90 or earlier? Use Markify › Check for Updates… instead; it installs 2.0.2 directly.

If you use the command line

The markify tool now lives in Contents/Helpers. If you linked it into your PATH, update the link:

ln -sf /Applications/Markify.app/Contents/Helpers/markify /usr/local/bin/markify

The Claude Code, Codex and OpenCode plugins find the new location on their own after you update them. See Command line.

Links

What you see

A <script> tag or an on… event handler (such as onerror) in a Markdown file was copied into the HTML file that Export › HTML writes. Opening the exported file in a browser ran it. Markify itself never ran the script, in the editor, PDF export or Quick Look.

What happened

HTML export wrote raw HTML as you wrote it, and its page had no Content-Security-Policy. PDF export and Quick Look already had one that blocks scripts.

Affected

Every version that has HTML export, and only for documents that contain scripts or event handlers. Ordinary documents export as before. Version 2.5.0 adds the policy to HTML export; the exported page keeps the HTML as written, but it does not run.

What to do

Install Markify 2.5.0 or later. Earlier versions: export only documents you wrote or trust to HTML, or use Export › PDF, which blocks scripts.

Links

What you see

On a keyboard that types accents with a dead key, the accent disappears and the next letter comes out plain: ´ then e gives e instead of é on a Spanish keyboard, ^ then e gives e instead of ê on a French one. Holding a letter down and picking the accent from the menu works.

What happened

A dead key leaves its accent waiting, underlined, for the next key. Markify refreshed the editor from the document before that key arrived, which removed the waiting accent and cancelled it. The keyboard itself has nothing to do with it.

Affected

Versions before 2.5.2, for anyone who types accents with dead keys: Spanish and French layouts, the US layout’s Option-key accents (Option-e then e for é), and other layouts with dead keys.

What to do

Install Markify 2.5.2 or later. Earlier versions: hold the letter down and choose the accent from the menu.

Links