Re: [Pharo-dev] Variables in auto-completion

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 th

Re: [Pharo-dev] Variables in auto-completion

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 wrote: > > > > --- > Julien Delplanque > Doctorant à l’Université de Lille > http://juliendelplanque

Re: [Pharo-dev] Variables in auto-completion

> On 28 Mar 2019, at 15:10, Alistair Grant wrote: > > On Thu, 28 Mar 2019 at 11:16, Cyril Ferlicot wrote: >> >> 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. >>

Re: [Pharo-dev] Variables in auto-completion

On Thu, 28 Mar 2019 at 11:16, Cyril Ferlicot wrote: > > 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. The current version rea

Re: [Pharo-dev] Variables in auto-completion

--- 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 a écrit : > > Hi, > > I remember that in old Phar

[Pharo-dev] Variables in auto-completion

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. The current version really annoys me since most of the time I would prefer to have a varia