[wsl] reopen should restore open editors

Open
#2,424 1 comment 0 reactions 1 assignee View on GitHub

@aeschli is already working on this.

Since Feb 25, 2020.

Assessment

This issue has not been assessed yet.

Description

feature-request wsl

Issue Type: Bug

When I Reopen folder in WSL or Reopen folder in Widows the open editors change. This is really inconvenient as I routinely switch back and forth for testing. I would expect this to be the default functionality, but since it isn't, it would be super nice if the editors/files open in one instance would be the same in the other after Reopening.

VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.4.0-17763-Microsoft

System Info
Item Value
CPUs Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 15.88GB (2.40GB free)
Process Argv
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu
OS Linux x64 4.4.0-17763-Microsoft
CPUs Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
Memory (System) 15.88GB (2.40GB free)
VM 0%
Extensions (10)
Extension Author (truncated) Version
xml Dot 2.5.0
Go ms- 0.13.0
vscode-yaml red 0.7.2
code-spell-checker str 1.7.24
vscode-docker ms- 0.10.0
remote-containers ms- 0.101.1
remote-ssh ms- 0.49.0
remote-ssh-edit ms- 0.49.0
remote-wsl ms- 0.42.3
vscode-remote-extensionpack ms- 0.19.0
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

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.

More from microsoft/vscode-remote-release

All issues in microsoft/vscode-remote-release

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.