microsoft / microsoft/vscode-remote-release

user should be shown the local backup version of the file, if remote SSH is disconnected during an unsaved edit.

Open
#11,637 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

This is partially relevant to #10799 and #8969 bugs.
I am requesting a UX feature for displaying the local code backup of an unsaved file after a remote session disconnection.
if remote SSH is disconnected during an unsaved edit of a remote file, the file cannot be saved either locally or remotely. There is a local backup of the file in a subdirectory of ~/Library/Application Support/Code/Backups (MacOS) or its platform equivalent. However neither the specific file location nor that code backup directory is not displayed to the user and non-expert users may not be aware a backup is present. I would have to go through most recently modified folders under ".../Code/Backups" to find the modified file and recover unsaved work.

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 implementation file or test is named. Start by reproducing a remote SSH disconnection during an unsaved edit and inspect the local backup under ~/Library/Application Support/Code/Backups or its platform equivalent. Done means the user is shown how to access the local backup of the unsaved remote file.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.