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

Feature-Request: cursorRedo / Soft Redo #82007

Closed
NotWearingPants opened this issue Oct 5, 2019 · 5 comments · Fixed by #82620
Closed

Feature-Request: cursorRedo / Soft Redo #82007

NotWearingPants opened this issue Oct 5, 2019 · 5 comments · Fixed by #82620
Assignees
Labels
editor-contrib Editor collection of extras feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@NotWearingPants
Copy link
Contributor

NotWearingPants commented Oct 5, 2019

There is a command called "cursorUndo" (name in command palette: "Soft Undo") that undo's cursor and selection movements.

There should be a matching "cursorRedo" (name in command palette: "Soft Redo") to redo those movements after undoing with "cursorUndo".

VSCode Version: 1.38.1
OS: Windows

@vscodebot
Copy link

vscodebot bot commented Oct 5, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@NotWearingPants NotWearingPants changed the title Feature-Request: Soft-Redo, and preserve Soft-Undo stack across undos Feature-Request: Soft-Redo Oct 5, 2019
@NotWearingPants NotWearingPants changed the title Feature-Request: Soft-Redo Feature-Request: Soft Redo Oct 5, 2019
@NotWearingPants NotWearingPants changed the title Feature-Request: Soft Redo Feature-Request: cursorRedo / Soft Redo Oct 5, 2019
@NotWearingPants
Copy link
Contributor Author

NotWearingPants commented Oct 5, 2019

This issue is different than the suggested duplicates.

@alexdima alexdima added editor-contrib Editor collection of extras feature-request Request for new features or functionality labels Oct 7, 2019
@alexdima alexdima added this to the Backlog milestone Oct 7, 2019
@alexdima alexdima removed their assignment Oct 7, 2019
@NotWearingPants
Copy link
Contributor Author

I am working on this. PR will be submitted soon.

@ejazr83
Copy link

ejazr83 commented Oct 15, 2019

I would like to propose a feature request to allow use of remote development feature of VScode when using remote Jupyter notebooks

Currently, to be able to execute remote Jupyter notebooks in VSCode, you need to have the Python runtime installed on your local machine.

To get the same benefits of remote VS Code development such as not requiring to install Python runtime, the Python Jupter remote execution should be able to run similar to a remote VS Code development environment.

Currently this works when you SSH to a box but it would be helpful if this can also be initiated when a remote Jupyter notebook is connected to so that the cells are run remotely rather than in local runtime

This will effectively make VS code use the remote runtime for the Jupyter notebooks rather than the local runtime removing the need to have Python installed locally for this use case.

Apologies @NotWearingPants , wrong place, problem with late night Github with too many wrokspaces open :)

Please ignore

@NotWearingPants
Copy link
Contributor Author

@ejazr83
Cool cool but what does it have to do with my cursor redo feature request?
Did you mean to report a new issue?

@alexdima alexdima modified the milestones: Backlog, October 2019 Oct 18, 2019
@alexdima alexdima added the verification-needed Verification of issue is requested label Oct 29, 2019
@jrieken jrieken added the verified Verification succeeded label Oct 29, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
editor-contrib Editor collection of extras feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants