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

CMD+D in new unsaved file #10075

Closed
normalser opened this issue Aug 3, 2016 · 10 comments
Closed

CMD+D in new unsaved file #10075

normalser opened this issue Aug 3, 2016 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@normalser
Copy link

  • VSCode Version: 1.4.0-insiders
  • OS Version: OSX

Steps to Reproduce:

  1. Have 1 existing file open in VSCode
  2. Click File/New (CMD+N) to create new unsaved file
  3. Paste
abc def
abc def
abc def
  1. Put cursor inside abc
  2. Hit CMD+D multiple times
  3. Problem: Nothing gets selected
@alexdima
Copy link
Member

@wallverb I cannot reproduce:

cmd-d

@alexdima alexdima added the info-needed Issue requires more information from poster label Aug 12, 2016
@alexdima alexdima added this to the Backlog milestone Aug 12, 2016
@normalser
Copy link
Author

Ok, so here are the steps that I can always reproduce on OSX (not sure if it's also problem on WIN)

  1. Have one (and only one file fully open that is from project)
  2. Press CMD+N to open new file/tab (don't double click tab bar because this way everything works ok for some reason)
  3. Type text, try to select first word with CMD+D - nothing happens

Here is the gif:
yifoad4ain

@alexdima
Copy link
Member

Thank you, I can reproduce with these steps! Root cause is the editorFocus context key, which gets set to true from a second CodeEditorWidget instance and then gets reset to false from the original CodeEditorWidget instance. Root cause is #10358.

@bpasero @jrieken Let's discuss tomorrow

@alexdima alexdima modified the milestones: August 2016, Backlog Aug 15, 2016
@alexdima alexdima added important Issue identified as high-priority and removed info-needed Issue requires more information from poster labels Aug 15, 2016
@jrieken jrieken self-assigned this Aug 15, 2016
@bpasero
Copy link
Member

bpasero commented Aug 15, 2016

Feel free to close as duplicate of #10358 unless there is something else we need to take care of?

@alexdima
Copy link
Member

I like that we finally have reproducible steps. @bpasero Let's discuss tomorrow, maybe we go back to having scoped contexts per editor instance.

@bpasero
Copy link
Member

bpasero commented Aug 15, 2016

@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).

@bpasero bpasero self-assigned this Aug 15, 2016
@bpasero
Copy link
Member

bpasero commented Aug 16, 2016

@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.

@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Aug 17, 2016
jrieken added a commit that referenced this issue Aug 22, 2016
…te a new context service when creating an editor, #10075
@jrieken jrieken closed this as completed Aug 22, 2016
@bpasero
Copy link
Member

bpasero commented Aug 22, 2016

@jrieken does this mean I can revert the change in textEditor.ts of e466584 ?

@jrieken
Copy link
Member

jrieken commented Aug 23, 2016

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

@bpasero
Copy link
Member

bpasero commented Aug 23, 2016

@jrieken 👍

@bpasero bpasero added the verified Verification succeeded label Sep 1, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants