Well... I disagree with your disagreement :) We are talking about two different things: 1) the current defaults 2) some possible broken configuration about the current defaults, "enter" is the one that is choose for 99% of IDEs around the world (and yes, the 1% default is probably just Pharo 1.4). so, we took the world default and placed there because we want to be friendly with newcomers (and frankly, I'm tired of see students learning Pharo pressing enter each time they want a completion and complaining when they don't have the answer they expect) The enter as default should stay, because that's the world standard. For power users like you, there is a settings browser to disable it... and you know, there is also a way to store your settings, so you can put them there and never ever in your life realize that you have different defaults. Now, in the settings: Go to code completion configuration: 1) Disable the option "Complete common prefixes using TAB in the suggested completions". This is for provide something like the bash completion (that completes until the chars are equal and allows you to introduce a character to continue refining the completion) 2) Disable the option "Use ENTER to accept a suggested completion" and then you have exactly the same behavior as before :) (but yes, the message explaining the options could be better) you can also then press "Export Settings" (button in top-right), and all your images will share same configuration. how to doit directly in the settings? go to ~/Library/Preferences/pharo/2.0 (for Mac) (if it does not exist, just create it) then create a file settings.st, with this content: StartupLoader default executeAtomicItems: { StartupAction name: 'Settings 2.0' code: [ NECPreferences expandPrefixes: false; useEnterToAccept: false. ] runOnce: true. }. I don't think that this is perfect, and there are some things that certainly can be enhanced... but you actually can configure your settings. It is impossible to believe that everybody will share same taste for programming, what you believe is obvious is obscure for others... that's why we try to match standards when we can, and to provide settings enough for those who does not follow them :) cheers, Esteban On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua@gmail.com> wrote:
On 3 April 2013 22:45, Camillo Bruni <camillobruni@gmail.com> wrote:
theres a setting to:
- disable ENTER to accept the completion - to increase the popup delay
so I think that is invalid bug report then...
i tend to disagree. The defaults which we have now in 2.0 for autocompletion is breaking my workflow badly too.
Yes, i can go to settings and disable/reconfigure stuff but that doesn't nullifying the fact, that my workflow is broken with ambiguous and inconsistent reaction(s) to my keystrokes by UI if i keep defaults.
For instance i am still clueless, why 'enter' is default for autocompletion, and disabling it and enabling 'tab' simply doesn't works. That leaves me with the only option: keep using 'enter' for autocompletion, if i ever want to use it. We have to fix that.
On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
From https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardne... :
The combination of enter on accept, with the current behavior to select the first completion suggestion by default = trouble. For example:
1. Type "printOn: aStream"... pretty common method start 2. Hit enter to go to the next line
You will now have "printOn: MCDataStream" WTF!! I get burned by this pretty regularly and it's annoying. I'm not sure what the fix should be... probably no default selection in the suggestion menu, but possibly only when enter on accept is enabled (t would require an extra key press to complete and when do you ever type a tab in the middle of a line?)
----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp4... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.