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

Backspace should not always cancel code completion #36491

dennisfrostlander opened this Issue Oct 18, 2017 · 0 comments


None yet
3 participants

dennisfrostlander commented Oct 18, 2017

  • 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 label Oct 19, 2017

@jrieken jrieken added this to the November 2017 milestone Oct 23, 2017

@jrieken jrieken changed the title from Backspace should not commit code completion to Backspace should not always cancel code completion Oct 31, 2017

@jrieken jrieken added bug and removed feature-request labels Nov 24, 2017

@jrieken jrieken closed this in e8a4084 Nov 24, 2017

@mjbvz mjbvz added the verified 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.