I'm fine with the fact that Pharo decides to put that as a default (because I
can change it).
But the preferences are fundamentally flawed: if I disable useEnterToAccept
then I cannot even use <tab> instead.
I should also disable the <tab> as the completion of common prefixes.
The change I attached to my email demonstrates that this should not be the case.
On 07 Apr 2013, at 12:27, Esteban Lorenzano <esteba...@gmail.com> wrote:
> I still think useEnterToAccept has to be true
> I sustain the idea of lower the entry level for the newcomers, instead
> supporting as default the use-workflow of power users (they have a settings
> browser there).
> We took this decision last year and I think it was a good one... not that we
> cannot change, but I would stick with it for now.
>
> I think the current completion functionality has some other problems that
> makes it sometimes uncomfortable to use...
>
> On Apr 7, 2013, at 12:16 PM, stephane ducasse <stephane.duca...@free.fr>
> wrote:
>
>>
>> On Apr 6, 2013, at 11:44 PM, Benjamin <benjamin.vanryseghem.ph...@gmail.com>
>> wrote:
>>
>>> If everybody likes it, maybe we should consider putting this configuration
>>> as default, no ?
>>
>> yes but first I would like to see the difference because I do not like it :)
>>
>>
>>> Ben
>>>
>>> On Apr 6, 2013, at 8:59 PM, "Sean P. DeNigris" <s...@clipperadams.com>
>>> wrote:
>>>
>>>> stephane ducasse wrote
>>>>> would it be possible to get a couple of settings that you use?
>>>>
>>>> NECPreferences
>>>> enabled: true;
>>>> caseSensitive: true;
>>>> expandPrefixes: true;
>>>> useEnterToAccept: false;
>>>> smartCharacters: true;
>>>> smartCharactersWithDoubleSpace: '[]{}';
>>>> spaceAfterCompletion: false;
>>>> popupAutomaticDelay: 100.
>>>>
>>>>
>>>>
>>>> -----
>>>> Cheers,
>>>> Sean
>>>> --
>>>> View this message in context:
>>>> http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp4679488p4679997.html
>>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>>>>
>>>
>>
>
