Ben, you have it! Just have the search-completion linked to ctrl+space!

Where is that setting ?

Thierry

Le 05/04/2013 14:38, Benjamin a �crit :

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

On Apr 5, 2013, at 2:12 PM, Sean P. DeNigris <sean@clipperadams.com
<mailto:sean@clipperadams.com>> wrote:

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
<http://Nabble.com>.

--
Thierry Goubier
CEA list
Laboratoire des Fondations des Syst�mes Temps R�el Embarqu�s
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95