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

Quickfix lightbulb appends to any existing command after applying #162216

Closed
connor4312 opened this issue Sep 28, 2022 · 8 comments · Fixed by #162701
Closed

Quickfix lightbulb appends to any existing command after applying #162216

connor4312 opened this issue Sep 28, 2022 · 8 comments · Fixed by #162701
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders terminal-quick-fix verified Verification succeeded
Milestone

Comments

@connor4312
Copy link
Member

connor4312 commented Sep 28, 2022

Testing #161846

  1. Do something that prompts a quick fix
  2. Start typing a command, then realize there's a suggested fix for it
  3. Accept the quickfix suggestion
  4. Notice the last command is appended to whatever you had typed in step 2

Could be fixed by:

  • Hiding the bulb if anything new is typed on the prompt
  • Clearing the prompt when applying the fix
  • Or just not appending the last command in the case something is already there
@Tyriar Tyriar added this to the October 2022 milestone Sep 28, 2022
@Tyriar
Copy link
Member

Tyriar commented Sep 28, 2022

How about a combination of the suggestions:

  • On user input, we hide the quick fix lightbulb but still allow it to be triggered via keybinding
  • When the lightbulb is hidden, we will run the same code to clear the command if needed as run recent command does (if we do this all the time you would see some ^C when we can't detect it)

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug terminal-quick-fix labels Sep 28, 2022
@connor4312
Copy link
Member Author

Sounds good to me 🙂

@meganrogge
Copy link
Contributor

On user input, we hide the quick fix lightbulb but still allow it to be triggered via keybinding

I don't think this aligns with the editor behavior and could be surprising if accidentally encountered

@meganrogge
Copy link
Contributor

In the editor, the lightbulb hides on input and only reappears if there's still a suggestion. IMO, we should just remove the lightbulb on input

@Tyriar
Copy link
Member

Tyriar commented Sep 29, 2022

@meganrogge a very real scenario is the user starts typing and only after that realizes the convenient quick fix though, which is what @connor4312 ran into. Hiding it while still allowing to trigger quick fixes until command executed would cover this case for users that know the keybinding, no downside afaict.

@meganrogge
Copy link
Contributor

users that know the keybinding I'd argue need less help 😄 so we should probably show the lightbulb until command execution

@Tyriar
Copy link
Member

Tyriar commented Sep 29, 2022

👍 as long as it's accessible is the main thing. Hard to say what feels better, I was thinking of it from a power user perspective; removing UI noise if it's unlikely to be used

@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Oct 6, 2022
@joyceerhl joyceerhl added the verified Verification succeeded label Oct 26, 2022
@joyceerhl
Copy link
Collaborator

Verified that quick fix lightbulb isn't hidden when input is entered, and if there's input entered a ^C is inserted before the actual quickfix is run

image

@github-actions github-actions bot locked and limited conversation to collaborators Nov 20, 2022
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 insiders-released Patch has been released in VS Code Insiders terminal-quick-fix verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants