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

Undo doesn't work in Notebook Cell #6960

Closed
rebornix opened this issue Aug 6, 2021 · 10 comments
Closed

Undo doesn't work in Notebook Cell #6960

rebornix opened this issue Aug 6, 2021 · 10 comments
Assignees
Milestone

Comments

@rebornix
Copy link
Member

rebornix commented Aug 6, 2021

Originally reported in microsoft/vscode#130142. Undo doesn't work in notebook.

@northernocean
Copy link

Just a note but there was a recent change in 1.59.0 that may be related:

From the release notes for Notebook layout improvements:

The default value of notebook.undoRedoPerCell is now changed to true.

@ghost
Copy link

ghost commented Aug 31, 2021

Any updates on this issue?

@ChHecker
Copy link

ChHecker commented Oct 5, 2021

Using version 1.21.8, I still encounter this issue. Any updates?

@J-Fields J-Fields added this to the Backlog milestone Oct 6, 2021
@edemaine
Copy link
Contributor

edemaine commented Oct 6, 2021

FWIW, . (repeat last command) also doesn't work within notebook cells. Presumably the same underlying issue.

@aromatt
Copy link

aromatt commented Nov 8, 2021

Does anyone have a workaround for this in the meantime?

@edemaine
Copy link
Contributor

edemaine commented Nov 8, 2021

The classic undo (Ctrl-Z on Windows) works, so that's what I use as a workaround in notebooks. But it doesn't always interact well with Vim commands.

@aromatt
Copy link

aromatt commented Nov 8, 2021

Thanks, @edemaine - that's what I'm doing for now too. I spent a few minutes trying to adjust configs so that the u vim binding works. Maybe it's easy, but I don't know enough about VS Code or these extensions.

@yannickdaniel
Copy link

I'm also interested in a solution / workaround. @aromatt did you find a fix yet?

@aromatt
Copy link

aromatt commented Dec 11, 2021

@yannickdaniel sorry to say I did not.

@bpkroth
Copy link

bpkroth commented Feb 1, 2022

@J-Fields any details on when a new release will be cut or how to produce one locally to test out your fix? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants