I personally solve that by disabling auto popup :)
And it fits in what Doru said.
I have to hit ctrl space to pops up completion, and here, I know that I am in completion mode, so pressing enter is not breaking my workflow.
Moreover, usually when I see people using completion, it's highly a lost of time.
the basic case is instead of fully typing 'asString', they type 'as', wait 3 seconds, press arrow down 20 times, and finally accept.
This is for me so strange :)
Maybe it's because I have been through a couple of Pharo version with auto completion disabled because it was a pain :D
Ben
EstebanLM wrote
Oh, Spotlight is another victim of the code completion lack of accurate
answers...
and yes, I agree: both code completion and spotlight in consequence were
working better in 1.4.
With enter-on-accept disabled, I'm really enjoying the completion in 2.0. I
find partial completions extremely helpful. I don't think we're that far
from where we want to be. Let's just define what's missing and get it done.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp4679488p4679787.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.