Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hex Editor displays unnecessary notification when a previously-opened file is deleted #428

Closed
joyceerhl opened this issue Mar 30, 2023 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@joyceerhl
Copy link

  1. Open a file in the hex editor
  2. Close the hex editor
  3. Delete the file
  4. 🐛 get this warning from the hex editor:

image

@cyjohnson-ss
Copy link

Confirmed

@AaronRidoutAE
Copy link

AaronRidoutAE commented Jun 20, 2023

There is another two parts to this issue that I see.

  1. Even though the file is closed, this still pops up and the 'Close Editor' button closes the current window - not the offending one (which in my case is already closed!). Please only close the offending window, not the current one!
  2. The pop up does not say which file it is warning about - I have many files open and one of them is transitory (being built in my case). Please add the filename to the pop-up!

@TheMatt2
Copy link

TheMatt2 commented Oct 25, 2023

Confirmed as well.

  1. Open a file in the hex editor
  2. Close the hex editor
  3. Open a different file
  4. Modify file
  5. Delete original file

If you click "Overwrite", nothing happens. The file is not restored.
If you click "Close Editor" then the other file is closed.

Any timeline when this will get integrated?

@Dream-Painter
Copy link

Confirmed, and it even happens multiple times.
I had a temp file, which is created and deleted multiple times, and I got multiple popups after opening it once.

@connor4312 connor4312 added the bug Issue identified by VS Code Team member as probable bug label Feb 1, 2024
connor4312 added a commit that referenced this issue Feb 2, 2024
@joyceerhl joyceerhl added this to the February 2024 milestone Feb 2, 2024
@DonJayamanne DonJayamanne added the verified Verification succeeded label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

8 participants