microsoft / microsoft/edit

The `Unsaved Changes` window behaves differently under the Exit and the Close operation.

Open
#271 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-bug E-help-wanted P-medium
Dominant language
Rust
Stars
14.6k
Forks
734
Avg merge
8h 40m
Merged PRs (30d)
4

Description

The window will not disappear if I select exit and save a file
### Exit

![Image](https://github.com/user-attachments/assets/5ece8069-d44b-487c-b166-a7de3d7cf050)

### Close

![Image](https://github.com/user-attachments/assets/733b9730-02b7-4455-b4f1-212ef5156b91)

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

Reproduce the `Unsaved Changes` window through both the Exit and Close operations, saving a file in each flow and comparing whether the window disappears. Trace the entry points for these two operations and the unsaved-changes prompt; done means both flows consistently dismiss the window after a successful save.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.