CLion Aggressive Auto Completion in Comments
CLion 2019.1.4
Build #CL-191.7479.33, built on May 30, 2019
JRE: 1.8.0_202-release-1483-b53 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.0.0-16-generic
Hi,
I'm trying to write some comments in my code, and autocompletion is being incredibly disruptive. E.g. trying to write the word "a" corrects it to "auto". Fixing it after it is autocorrected is also really cumbersome. Please see my video for details.
As stated in the video, I've tried disabling all settings under Editor -> General -> Code Completion to no avail.
This occurs for both line comments and block comments.
Any help would be greatly appreciated, I thought I might just be missing something obvious, but if not and it is indeed a bug I will go post an issue on YT.
Regards
请先登录再写评论。
Hi! So far I can't reproduce it on my side. Is there any chance that some other program on your machine does this autocompletion? Do you observe this behavior only in CLion?
Hi Anna, thanks for the response.
This seems to still be occurring in CLion 2019.2, with all downloaded plugins disabled.
To try and answer your question... This behaviour is only observed in CLion, and I don't know of any other program on my system which would have this capability. I'm running CLion on Kubuntu 19.04.
I have some more information about the issue: it occurs in string literals, comments, and the start of declarations, and so far I have only found these occurrences:
Interestingly, it only autocompletes when typing a single letter; completing more of the word (like doing "au" instead of "a") doesn't autocomplete. So there is some specific autocomplete feature for these single letters when typed on their own.
So... is this an intended feature of CLion? If it is, it probably shouldn't be doing it in comments and string literals :)
Regards
Ah, I found the feature. It is of course Editor -> Live Templates. I can't seem to find a report on YouTrack for live templates completing in comments and string literals, so I'll do some further inspection and go post one.
Edit: Issue is posted here
Thanks for investigating and creating the issue!