>
>
> Message: 4
> Date: Wed, 4 Aug 2010 02:09:57 +0100
> From: Tim Mackinnon
> Subject: Re: [Pharo-project] Refactor source method is grayed out?
> To: Pharo-project@lists.gforge.inria.fr
> Message-ID: <69eb6bbc-fa35-4168-a291-7e3c956dc...@gmail.com>
> Con
Lucas - I can't repeat this in a Pharo 1.1 image - so maybe we should
put it down to some oCompletion/eCompletion bad interaction (or unload
weirdness).
Tim
On 3 Aug 2010, at 12:23, Lukas Renggli wrote:
I am using the images from hudson.lukas-renggli.ch. I don't know how
oCompletion depend
doru
please stop this insane appetizer for OCompletion, I have to work on latex
documents and integrate code no
fun programming right now ;D
Stef
On Aug 3, 2010, at 1:38 PM, Tudor Girba wrote:
> Hi,
>
> OCompletion forked the code from ECompletion and it now builds on it. I think
> the reas
Hi,
OCompletion forked the code from ECompletion and it now builds on it.
I think the reason for this fork was that at the time when Romain
started there was nobody really maintaining ECompletion.
But, it would be great to have just one completion mechanism. I highly
suggest to take a loo
I am using the images from hudson.lukas-renggli.ch. I don't know how
oCompletion depends/overrides on eCompletion, so indeed it might make
a difference.
Lukas
On Tuesday, August 3, 2010, Tim Mackinnon wrote:
> Lucas, which image are you using - and I will load it up and try again (I am
> using
Lucas, which image are you using - and I will load it up and try again
(I am using the seaside 3.0rc image - although I did unload
oCompletion from it and then load eCompletion - maybe that makes a
difference?). I appreciate your patience on this by the way - often
I'm not sure which things
I played a bit with the selection an the enabling of the menus this
morning, however I found it quite confusing if the closest matching
expression is automatically picked.
I could not reproduce the issue you report with the spaces. In my
image when I select a full expression whitespaces at start a
Lukas - I logged it as issue 2742 (now that I know its a bit picky,
I'll select extra spaces as a workaround).
Some day I will learn how some of this works so that I can try and
help out (from my time spent in Dolphin where RB is tightly
integrated, it was cool messing around with parse no
> Lukas, that doesn't seem right, as I had to do it manually and it seems to
> work fine in my code (maybe it wasn't clear what was trying to extract)?
Sorry, I misread your mail. I thought you talked about 'extract to
method', not 'extract to temporary'.
> nextEditorCharacter := (editor text at
Lukas, that doesn't seem right, as I had to do it manually and it
seems to work fine in my code (maybe it wasn't clear what was trying
to extract)?
- e.g.
nextEditorCharacter := (editor text at: editor startIndex ifAbsent:
[nil ]).
(opposite = aCharacter and: [ nextEditorCharacer = aChara
On 2 August 2010 15:13, Tim Mackinnon wrote:
> I was having a look at some of the ecompletion code - and noticed that I
> couldn't do an extract to temporary refactoring because the refactor source
> method is grayed out?
>
> This looks like a bug - and I'm happy to report it - but just wanted to
I was having a look at some of the ecompletion code - and noticed that
I couldn't do an extract to temporary refactoring because the refactor
source method is grayed out?
This looks like a bug - and I'm happy to report it - but just wanted
to check with people here.
The code fragment in q
12 matches
Mail list logo
