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.

Sign up for GitHub

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

Jump to bottom

Backspace should not always cancel code completion #36491

Closed
defr0std opened this issue Oct 18, 2017 · 0 comments
Closed

Backspace should not always cancel code completion #36491

defr0std opened this issue Oct 18, 2017 · 0 comments
Assignees
@jrieken
Labels
bug Issue identified by VS Code Team member as probable bug suggest IntelliSense, Auto Complete verified Verification succeeded
Milestone
November 2017

Comments

@defr0std
Copy link

defr0std commented Oct 18, 2017 •
edited

  • VSCode Version: 1.17.0
  • OS Version: Any

Steps to Reproduce:

  1. Open your most beloved project in VSCode.
  2. Start typing in any code file to trigger the code completion.
  3. Imagine you made a typo and press backspace while code completion is still displayed.

Expected: code completion should be re-triggered.
Actual: code completion is done and you need to trigger it manually again.

A number of inconveniences have been already reported in issue #19238.
This behavior is not consistent with other editors, including the big-VS.

Could you please reconsider the default behavior or at least provide a setting to change it?
@mjbvz mjbvz added the suggest IntelliSense, Auto Complete label Oct 19, 2017
@jrieken jrieken added the feature-request Request for new features or functionality label Oct 23, 2017
@jrieken jrieken added this to the November 2017 milestone Oct 23, 2017
@jrieken jrieken changed the title Backspace should not commit code completion Backspace should not always cancel code completion Oct 31, 2017
@jrieken jrieken added bug Issue identified by VS Code Team member as probable bug and removed feature-request Request for new features or functionality labels Nov 24, 2017
@mjbvz mjbvz added the verified Verification succeeded label Dec 6, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jrieken jrieken

Labels
bug Issue identified by VS Code Team member as probable bug suggest IntelliSense, Auto Complete verified Verification succeeded
Projects
None yet
Milestone
November 2017
Development

No branches or pull requests
3 participants
@jrieken @mjbvz @defr0std