-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Please add the file/folder cut command to the context menu and the releated shortcut. #61110
Labels
feature-request
Request for new features or functionality
file-explorer
Explorer widget issues
on-testplan
release-notes
Release notes issues
Milestone
Comments
no response?? |
We will discuss this in this week's ux meeting and we will let you know what we decide. |
isidorn
added
the
under-discussion
Issue is under discussion for relevance, priority, approach
label
Oct 23, 2018
ok, thanks! for my conern, this should not be put in any extension. this is a feature to make vscode a true files edit |
isidorn
added
feature-request
Request for new features or functionality
verification-needed
Verification of issue is requested
and removed
under-discussion
Issue is under discussion for relevance, priority, approach
labels
Jan 18, 2019
You can try this out from tomorrow's vscode insiders |
isidorn
added
on-testplan
and removed
verification-needed
Verification of issue is requested
labels
Jan 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feature-request
Request for new features or functionality
file-explorer
Explorer widget issues
on-testplan
release-notes
Release notes issues
vscode is a code editor, and cut/paste should be in Explorer View, and it is not related to any extensions, it is basic file operation...
without this command the file management functionality is not complete!
since the file/folder drag drop function is available, why this command is not available!
it's really strange this feature request is closed #57616. please value the voice from vscode fans!
The text was updated successfully, but these errors were encountered: