MacDownApp / MacDownApp/macdown
Quit MacDown without saving
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Slightly related to old #795
Here is how my morning went: I glanced at a project README.md in MacDown and decided to redo it in Vim. Once finished, I took a look at it in again MacDown. Then I quit MacDown and was presented with the question:
* Save
* Revert changes
* Cancel.
I assumed "save" will overwrite and "cancel" is to abort the quitting and "revert" is your typical "discard changes" button. But no. Revert dug up the original file from somewhere(?) and wrote it over the README.md I spent the whole morning writing in vim.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the README.md and Vim workflow described in the issue, then inspect MacDown’s quit and unsaved-changes flow. Determine how the Save, Revert changes, and Cancel actions are presented and handled; done means quitting no longer unexpectedly overwrites newer external edits and the available choices match their labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, objective-c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100