New SciTE4AutoIt3 available with updated SciTE v3.4.1

[mLipok]

mLipok,

When I test your posted code, the end result depends on what key I press:

 

- If I press {SPACE} I always get the abbreviation expanded,

- If I press {ENTER} I always get the function name.

Which is exactly what I would expect. What key are you pressing each time?

Anyway, why not just rename the function so that the naming conflict is no longer present?

M23

 

 

For0UBound()    is not my function, and I hate it. You can take it from me.

I trying to use Abbreviations in my daily work.

for0ub is abbreviation defined in: "c:UsersuserAppDataLocalAutoIt v3SciTEau3abbrev.properties"

for0ub=For $i = 0 To UBound(|) -1

[Melba23]

mLipok,

I realise that for0ub is an abbreviation - but I am asking you which key you press when the abbreviation is typed and the autocomplete dialog suggests the function name. When I enter that code into SciTE the result is determined by which key I press: {SPACE} expands the abbreviation while {ENTER} autocompletes the function name - this behaviour is entirely as expected. Please can you test on your system by entering the code twice and pressing the 2 different keys in the 2 instances.

And if anyone else wants to try - please do and let us know the result.

M23

[mLipok]

I press SPACEBAR == {SPACE}.

I'd love to check exactly what you say, but for the moment I have to re-test be desirable environment in which the error is repeatable.
And it's not that simple .

[mLipok]

One more observation:

when I try

for0ub{SPACE}

all is ok

when i try

For0ub{SPACE}

then it appear

different: first char is big.

EDIT:

when I try

For0ub{ENTER}

then nothing unexpected happend, just normal new line.

Edited July 2, 2014 by mLipok

[Melba23]

mLipok,

Abbreviations will only expand if they are entirely in lower-case - they still appear in the abbreviation syntax colouring if there are upper-case letters but they will not expand.

But now you have mentioned the case difference I can indeed reproduce what you are seeing - when the initial letter is upper-case then pressing {SPACE} does indeed autocomplete the function name. But I have no idea why - other than it must be happening because of the naming conflict between the function and the abbreviation. We will have to wait for Jos and see if he can shed any light on the matter.

M23

[mLipok]

But now you have mentioned the case difference I can indeed reproduce what you are seeing - when the initial letter is upper-case then pressing {SPACE} does indeed autocomplete the function name. But I have no idea why - other than it must be happening because of the naming conflict between the function and the abbreviation. We will have to wait for Jos and see if he can shed any light on the matter.

 

haha... I caught you maggot (issue / bug - not you M23 ).

change this

ub=UBound(|)

to this

ub=UBouTESTnd(|)

restart SciTE and try again.

[mLipok]

btw.

be careful:

almost entire content of au3abbrev.properties is duplicated inside this file.

I report this to Jos few day ago and he already fix it.

Edited July 2, 2014 by mLipok

[mLipok]

I make my own calltips api file:   au3.QuickPDF.calltips.api

 

I know I can add this in this way:

# Autocomplete and call tip settings
api.$(au3)=$(SciteDefaultHome)apiau3.api;$(SciteDefaultHome)apiau3.autoit3wrapper.api;$(SciteUserHome)au3.user.calltips.api;$(SciteUserHome)au3.QuickPDF.calltips.api

 

but I want to ask about that way:

# Autocomplete and call tip settings
api.$(au3)=$(SciteDefaultHome)apiau3.api;$(SciteDefaultHome)apiau3.autoit3wrapper.api;$(SciteUserHome)au3.user.calltips.api;$(SciteUserHome)au3.*.calltips.api

 

 

QUESTION:

Can this feature be added to S4A ?

In this way the only one thing will be to copy file 

au3.QuickPDF.calltips.api >>> SciteUserHome

 

EDIT:

or,

can you add a new feature to SciTE Config / CallTip Manager 

I mean function which chceck list of all 

au3.*.calltips.api

and add new ones to 

au3.properties

Edited July 2, 2014 by mLipok

[Jos]

Looks indeed that SciTE expands ub in stead of taking the whole string.

I can also replicate this by adding ubxub=test to au3abbrev.properties and typing UBxub and then pressing Ctrl+B (Expand).

Guess this is something in the SciTE internals acting this way.

Jos

[mLipok]

good to know because I've a few days I thought I lost my mind

[Jos]

what about au3.autoit3wrapper.api ?

Is part of the next update.

[Jos]

I make my own calltips api file:   au3.QuickPDF.calltips.api

 

I know I can add this in this way:

 

but I want to ask about that way:

 

QUESTION:

Can this feature be added to S4A ?

In this way the only one thing will be to copy file 

au3.QuickPDF.calltips.api >>> SciteUserHome

 

EDIT:

or,

can you add a new feature to SciTE Config / CallTip Manager 

I mean function which chceck list of all 

au3.*.calltips.api

and add new ones to 

au3.properties

 

Let's keep this simple and use the au3.user.calltips.api for user defined stuff... it is complex enough as it is for most.

Jos

[Jos]

Looks indeed that SciTE expands ub in stead of taking the whole string.

I can also replicate this by adding ubxub=test to au3abbrev.properties and typing UBxub and then pressing Ctrl+B (Expand).

Guess this is something in the SciTE internals acting this way.

Jos

Just checked the source and can confirm this is a feature, not a bug.

Jos

// Try each potential abbreviation from the first letter on a line
    // and expanding to the right.
    // We arbitrarily limit the length of an abbreviation (seems a reasonable value..),
    // and of course stop on the caret.
    while (abbrevLength > 0) {
        data = propsAbbrev.Get(abbrev);
        dataLength = data.length();
        if (dataLength > 0) {
            break;  /* Found */
        }
        abbrev++;   // One more letter to the right
        abbrevLength--;
    }

[Jos]

Uploaded new Beta SciTE merged with the v 3.4.4 changes released today.

Jos

Edited July 3, 2014 by Jos

[Melba23]

Jos,

 

Just checked the source and can confirm this is a feature, not a bug

M23

[mLipok]

 

Just checked the source and can confirm this is a feature, not a bug.

Jos

// Try each potential abbreviation from the first letter on a line
    // and expanding to the right.
    // We arbitrarily limit the length of an abbreviation (seems a reasonable value..),
    // and of course stop on the caret.
    while (abbrevLength > 0) {
        data = propsAbbrev.Get(abbrev);
        dataLength = data.length();
        if (dataLength > 0) {
            break;  /* Found */
        }
        abbrev++;   // One more letter to the right
        abbrevLength--;
    }

 

Can it be disabled ?

[Jos]

Can it be disabled ?

Of cource it could but we don't want that. the idea is described in the Helpfile:

 

When expanding, the names don't need to be separated from the previous text. Ie. if you define 'é' as 'é', you can expand it inside a word.

When multiple abbreviation names match, the longest matching name will be expanded.

 

This means that it will try to find the longest Abbreviation infront of the caret position even when the caret is located inside of a word.

Jos

[FaridAgl]

Jos,

About the /rm option of Au3Stripper, why should someone think about disabling it?

[Jos]

Jos,

About the /rm option of Au3Stripper, why should someone think about disabling it?

not sure I understand the question. Where is this stated?

[FaridAgl]

Sorry for not being so clear.

I meant /rm option is really good? Why should someone disable it while compiling the source?

I was suggesting to make it enable by default.