Marknote — Issues

Public issue tracker for Marknote, a native WinUI 3 markdown editor for Windows.

The application source lives in a private repository; this repo exists so users can file bug reports and feature requests with a public trail.

Reporting a bug or requesting a feature

The easiest way is from inside Marknote:

About → Report a bug · About → Request a feature

That opens a pre-filled issue here with your version, OS, .NET runtime, settings path, active vault, and a tail of any recent crash log already attached. You can review and edit everything in the browser before posting.

If Marknote won't launch, open an issue manually via the bug report form or feature request form.

What to include

Bug reports are easiest to act on when they include:

• Steps to reproduce — what you did, in order.
• Expected result — what you thought would happen.
• Actual result — what actually happened.
• Diagnostics — Marknote attaches these automatically; if you're filing manually, the version + OS + .NET runtime triplet is the minimum.
• Crash log — at %LOCALAPPDATA%\Marknote\crash.log. The in-app form includes the tail automatically.

What's not tracked here

• Source code, PRs, or commits — those live in the private repo.
• Security issues — please email support@marknote.md directly so the disclosure can stay confidential until a fix ships.
• General support questions — support@marknote.md for those too.

Triage labels

• bug — something doesn't work as documented.
• enhancement — feature request or improvement to existing behaviour.
• question — needs clarification before triage.
• wontfix — out of scope or by design.
• duplicate — already filed elsewhere; linked to the original.

Links

• Marknote website — https://marknote.md
• Privacy policy — https://marknote.md/privacy
• Terms — https://marknote.md/terms
• Support email — support@marknote.md