The globals are in the list first... I think this can be fixed by moving the adding from #initializeSelectors to #addVariables (class NECUntypedModel). The whole NEC code is far too complex⦠we have some experiments for an AST based version, we should dig that out again. (I added the note to the issue)
On 28 Mar 2019, at 15:32, Tim Mackinnon <tim@testit.works> wrote:
Yes - I noticed that too and raised a similar issue: https://github.com/pharo-project/pharo/issues/2855
On 28 Mar 2019, at 10:48, Julien <julien.delplanque@inria.fr> wrote:
--- Julien Delplanque Doctorant à lâUniversité de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq Numéro de téléphone: +333 59 35 86 40
Le 28 mars 2019 à 11:15, Cyril Ferlicot <cyril.ferlicot@gmail.com> a écrit :
Hi,
I remember that in old Pharo versions, the auto-completion added the variables at the top of the completion list. Now they are at the bottom under the classes.
The original version worked better for me.
I preferred previous version as well.
Cheers,
Julien
The current version really annoys me since most of the time I would prefer to have a variables completed. Is there a setting somewhere to get the old behavior back? If not, does someone knowing the implementation of the auto-completion knows where I could put a metalink to get the old behavior back for me?
-- Cyril Ferlicot https://ferlicot.fr