Can I tone down autocomplete a bit? Follow
At this point I'm being presented with several *classes* that start with timeline. Then I typed colen ( ':' ) and get an autocomplete to one of the classes.
Why should this happen? And why would I be presented with classes at that point in any case?
Please sign in to leave a comment.
I second this. The autocomplete in the 0.4.833 version of Scala plugin is more than annoying.
To the list of autocomplete misfeatures I would add:
1. Replacing "math." with "Math." - whenever I want to write e.g. "math.max", after I hit "." it capitalizes "m" because it thinks I wanted to use object Math and not package math.
2. Putting caret at the wrong position when writing "println" - the autocomplete autocompletes "()" after println and the caret is placed AFTER ")" instead of inbetween the brackets. If I press ESC after writing println to shut the autocomplete up, press "(", now the IntelliJ IDEA adds the missing ")" but the caret is placed correctly, so now I can immediately type the argument.
So, to summarize - if I type fast, the autocomplete should not interfere and the result should be exactly as I typed. Maybe add a small delay like 2s or so until it is more clever? Or make the spacebar cancel autocomplete, not apply it?
Eager completion for whatever identifiers is fixed now.
There's also an annoying issue where ClassName completion triggered through regular completion is inserting an unwanted "" after a type:
Using 961, code completion seems definately toned down. The problem is that often I won't get any suggestions (mainly for class names) even after hitting ctrl+space or ctrl+alt+space.
Using 949, the issue with println() autocompletion is still present. IMHO, the autocomplete *should not* treat typing "(" as accepting the autocomplete proposition, especially if there are more methods with the same name (as in println). If I really wanted it, I would press Enter instead of typing "(".
That's fixed now.
That's also fixed now. Class name completion now work as expected.
1. I can't reproduce it now. It seems this problem was about class name completion.
2. You can disable preselecting first position: Settings -> Editor -> Code Completion -> Preselect first position -> Never. (then you can use Tab to accept completion)
Also I'll think about how to fix sorting to place on first position functions with parameters, but I'm not sure that it's possible.
Sorting is also fixed now.
I'm running a local build post 968 and completion seems quite smooth :)
I have more issues about completion, and you should know them to avoid problems.
When you type "List" (the worst example) you can get class name autocompletion, and imported List (or implicitly imported from Predef) is not on first position. So you can accidently choose wrong variant because of autopopup completion (then this List will be autoimported). I'll try to fix it soon.
I've noticed that one as well, I was about to report it.
Is there a ticket for it already?
No, there is no ticket about it. I'm in progress to fix it in general.
If after that you find some examples where you think some lookup should be on first place, please report me.
That is fixed now. Please note, that it's work only for relevant sorting. For alphabetical sorting I created issue: http://youtrack.jetbrains.net/issue/IDEA-69247
One issue I noticed is that the "import exclusion popup" seems to offer duplicated entries:
Thanks for the improvements,