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

Unable to copy files across VSCode windows in 1.31 #68031

Closed
mooncake4132 opened this issue Feb 7, 2019 · 2 comments
Closed

Unable to copy files across VSCode windows in 1.31 #68031

mooncake4132 opened this issue Feb 7, 2019 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release regression Something that used to work is now broken verified Verification succeeded

Comments

@mooncake4132
Copy link

  • VSCode Version: Confirmed in 1.31 and the latest insider.
    Version: 1.32.0-insider
    Commit: d9f81c8
    Version: 1.31.0 (system setup)
    Commit: 7c66f58

  • OS Version:Windows_NT x64 10.0.17134

Steps to Reproduce:

  1. Open an arbitrary folder in vscode (call it vscode 1)
  2. Create a new vscode window (call it vscode 2) and open another arbitrary folder.
  3. Create a file in vscode 1.
  4. Ctrl+C or select copy from the right-click menu of the file in vscode 1.
  5. Attempt to paste the file in vscode 2 with Ctrl+V doesn't work. The "paste" menu item in the right-click menu is also grayed out.

This used to work in 1.30.2.

Does this issue occur when all extensions are disabled?: Yes

@iainvm
Copy link

iainvm commented Feb 7, 2019

Even dragging the files instead of ctrl+c and ctrl+v it will only move files, not folders.

Open all the directories ctrl+a (which is a nice new feature). Drag over to the 2nd windows workspace, and all you'll get is files, not folders.

OS Version: 4.20.5-arch1-1-ARCH

@bpasero bpasero self-assigned this Feb 7, 2019
@bpasero bpasero added candidate Issue identified as probable candidate for fixing in the next release regression Something that used to work is now broken labels Feb 7, 2019
@bpasero
Copy link
Member

bpasero commented Feb 7, 2019

PR: #68104

@bpasero bpasero mentioned this issue Feb 8, 2019
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Feb 8, 2019
@bpasero bpasero closed this as completed Feb 8, 2019
@sandy081 sandy081 added the verified Verification succeeded label Feb 12, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release regression Something that used to work is now broken verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants