marktext / marktext/marktext

Add Option to Disable Save Prompt on Exit

Open
#3,883 2 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:unicorn: feature request 🔭 area/ui
Dominant language
TypeScript
Stars
61.6k
Forks
4.6k
Avg merge
23h 49m
Merged PRs (30d)
89

Description

Describe your feature request
I would like to request an option in Mark Text that allows users to disable the save prompt when exiting a markdown file in edit mode, even if no changes have been made. This feature would help improve the user experience by removing the unnecessary prompt, which can be disruptive during regular usage.

What problem does this feature solve?
Currently, Mark Text defaults to edit mode when opening a markdown file, and even if no changes are made, it prompts the user to save the file upon exiting. This behavior can be annoying and unnecessary, especially for users who prefer to exit without having to confirm saving every time.

Additional context
It would be helpful if there was a setting or toggle in the preferences to disable this behavior, so that users can exit without seeing the save confirmation dialog, even if no changes were made.
The option could be something like "Disable save prompt on exit when no changes are made."
This would provide more flexibility and a smoother experience when using Mark Text for quick edits.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by locating the exit save-confirmation flow and the preferences UI, then trace how the app determines whether a document has changes. Done means a preference can disable the prompt specifically when no changes were made, while the existing save protection remains for modified files.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.