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

'u' should clear modified flag #565

Closed
localvar opened this issue Aug 5, 2016 · 7 comments
Closed

'u' should clear modified flag #565

localvar opened this issue Aug 5, 2016 · 7 comments

Comments

@localvar
Copy link

localvar commented Aug 5, 2016

What did you do?

open a file
do some editing
u to undo all editing
close the file

What did you expect to happen?

the file be closed

What happened instead?

VSCode asks: Do you want to save the changes you made to xxxxx?

Technical details:

  • VSCode Version: 1.4.0
  • VsCodeVim Version: 0.1.4
  • OS: Windows 10 Professional
@johnfn
Copy link
Member

johnfn commented Aug 5, 2016

I wish... Unfortunately, this is something that VSCode won't let us do currently.

@rebornix
Copy link
Member

rebornix commented Sep 8, 2016

Currently we are doing undo ourselves but I'm thinking this issue can be mitigated by setting correct undo stop and trigger Code's undo functionality.

@johnfn
Copy link
Member

johnfn commented Sep 8, 2016

Yeah, they do provide the API now! However, it would not be a straightforward change. On top of porting our history tracking code, you'd also have to get the remapper to work, which depends on reversing individual keystrokes (jj => esc reverses both j's, even though they wouldn't be separate undo steps).

@rebornix
Copy link
Member

rebornix commented Sep 8, 2016

@johnfn true. I'll have another round of sync up about the history access this afternoon and then let's how can we improve.

@enkeyz
Copy link

enkeyz commented Jun 1, 2018

Any progress on this? #2378

@dderg
Copy link
Contributor

dderg commented Jul 16, 2019

That's one of few things that prevents me from using vscode =(

@J-Fields
Copy link
Member

Closing in favor of #3201

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