Replies: 3 comments
-
I second this |
Beta Was this translation helpful? Give feedback.
0 replies
-
Related to #36266 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Related? #9978 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Synopsis:
Because copilot can produce suggestions at whitespace and because it can produce them faster than the key-repeat/typing speed of a human, it surfaces issues with IDE input mechanisms that aren't usually apparent to the user. In particular, it can generate a suggestion within two keystrokes causing input-fighting.
Description:
We have a whitespace-OCD codebase where things need to be lined up, which is antithetical to many modern BCPs and style guides, but it's what I have to work in.
The result is an incredibly unpleasant experience working with co-pilot because it becomes virtually impossible to add indentation by pressing tab.
Specifically: I press tab and a suggestion I never saw gets inserted.
I could accept that it's simply happening so quickly that I haven't registered it, but if that were the case then pressing esc,tab or tab,ctrl+z,esc,tab should work.
They don't.
I've tried waiting 1 and 2 beats longer before pressing esc, doesn't work. If I press esc before the suggestion is visible (and I mean as in the input needs to be processed on or after the screen refresh where the suggestion is rendered) then pressing tab will insert the suggestion.
Obviously this only affects tab, perhaps it would make sense to allow a delay after pressing tab in the 280-350ms range.
It should be possible to press tab twice quickly in the editor without that equating to "tab + suggestion".
-Oliver
Beta Was this translation helpful? Give feedback.
All reactions