Feature Suggestion / Request - Implement a way to disable intellisense/autocomplete/code suggestion popup until keypress
Hi,
I am not sure if feature requests are accepted here, but here is something that I and I believe many others would really benefit from, so I thought perhaps it was worth raising the issue.
Here's my suggestion, and motivation for it:
Sometimes when editing code, the user want's to be able to see the lines near the currently editing line. Perhaps they are copying some info for example.
The automatic code completion popup is sometimes a distraction and can block important lines of code that the user wants to be able to read.
For example, sometimes the user will be writing a function call and the editor will popup the lists of available function calls, differing by their arguments. I am not sure if this only happens with the C++ extentions installed.
It would be really great if there was a way to disable this automatic popup, unless a particular key combination is pressed. Sometimes it is very useful to be able to see which function calls are available, but often this isn't wanted and having the popup appear automatically is a distraction, particularly as it can steal user keypresses (up/down/left/right/enter/tab/etc).
I am aware the keypresses can be re-assigned, but having a way to disable the popup from appearing automatically, and then having a key combination to make it show up would be ideal!
Today I discovered the keyboard shortcut CTRL + I. I think this is related to the feature I was requesting above. It may have been added recently, I am not sure about that. I don't recall seeing it when I searched previously.
By default CTRL+ I is mapped to "Trigger Suggest" as well as "toggleSuggestionDetails".
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.