-
Notifications
You must be signed in to change notification settings - Fork 29.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
CMD+D in new unsaved file #10075
Comments
Ok, so here are the steps that I can always reproduce on OSX (not sure if it's also problem on WIN)
|
Feel free to close as duplicate of #10358 unless there is something else we need to take care of? |
I like that we finally have reproducible steps. @bpasero Let's discuss tomorrow, maybe we go back to having scoped contexts per editor instance. |
@alexandrudima I am fine revisiting that (as I have not yet started to work on disposing the editor) but I can reproduce the other issues as well easily as soon as I bring in the settings editor. Note that untitled files also use a different editor compared to files (the same editor that settings are using), so it is similar to opening settings (but likely easier to reproduce). |
@alexandrudima @jrieken after talking briefly to Alex, Joh is trying to bring back the state of having a keybinding service per editor. That means I will not continue in #10358 for now. |
…te a new context service when creating an editor, #10075
Why would you do that? I think not listening to events when you are invisible and potentially never visible again is generally a good thing |
@jrieken 👍 |
Steps to Reproduce:
abc
CMD+D
multiple timesThe text was updated successfully, but these errors were encountered: