Jos

Uploaded a fix for that issue to Beta Tidy v 25.205.1420.6

Uploaded a fix for that issue to Beta Tidy v 25.205.1420.6

Uploaded a fix for that issue to Beta Tidy v 25.205.1420.6

Uploaded a fix for that issue to Beta Tidy v 25.205.1420.6

Are you sure about that? Strait from the helpfile:
Jos 

I remember looking at this and there is a comment about it, but your scenario is still going wrong. try current beta lua script. 🙂  

The Full separate SciTE4AutoIt3 should work fine when setup for python correctly. 
Adding those to the python.properties and adding the actual python.api should be enough, but with the proper syntax:
api.$(file.patterns.py)=$(SciteDefaultHome)\api\python.api  
ps: This isn't really a SciTE support forum! 😉
 

Sorry for being slow here and understand the issue now...  Many ( really many) moons ago I moved all properties files into their own subdirectory, but AutoIt indeed install it into the SciTE root directory since that is also where the light version expects it.
Funny this comes up after such a loooong time, but I will have a look to fix this in the SciTE4AutoIt3  installer.
 
Guess all i really need to do is change this in au3.properties:
# Import the default au3.keywords.properties file containing AutoIt3 info import properties\au3.keywords # override with the AutoIt3 provided file located in the root. import au3.keywords  

Sorry for being slow here and understand the issue now...  Many ( really many) moons ago I moved all properties files into their own subdirectory, but AutoIt indeed install it into the SciTE root directory since that is also where the light version expects it.
Funny this comes up after such a loooong time, but I will have a look to fix this in the SciTE4AutoIt3  installer.
 
Guess all i really need to do is change this in au3.properties:
# Import the default au3.keywords.properties file containing AutoIt3 info import properties\au3.keywords # override with the AutoIt3 provided file located in the root. import au3.keywords  

Sorry for being slow here and understand the issue now...  Many ( really many) moons ago I moved all properties files into their own subdirectory, but AutoIt indeed install it into the SciTE root directory since that is also where the light version expects it.
Funny this comes up after such a loooong time, but I will have a look to fix this in the SciTE4AutoIt3  installer.
 
Guess all i really need to do is change this in au3.properties:
# Import the default au3.keywords.properties file containing AutoIt3 info import properties\au3.keywords # override with the AutoIt3 provided file located in the root. import au3.keywords  

Sorry for being slow here and understand the issue now...  Many ( really many) moons ago I moved all properties files into their own subdirectory, but AutoIt indeed install it into the SciTE root directory since that is also where the light version expects it.
Funny this comes up after such a loooong time, but I will have a look to fix this in the SciTE4AutoIt3  installer.
 
Guess all i really need to do is change this in au3.properties:
# Import the default au3.keywords.properties file containing AutoIt3 info import properties\au3.keywords # override with the AutoIt3 provided file located in the root. import au3.keywords  

Nope, you are restoring a proper version of a file which likely was accidentally changed. 😀

No, you should not add anything to that file as it is overwritten with autoit3 installs. 😉

No, you should not add anything to that file as it is overwritten with autoit3 installs. 😉

You know I will need details on what you have installed to have any clue why that happens, but in general when you open "au3.keywords.properties" from within SciTE/Options, you get the file that is used to recognize the UDFs. 

Uploaded an updated Beta version of SciTE zipfiles containing a fix for the lexer colors.

Uploaded an updated Beta version of SciTE zipfiles containing a fix for the lexer colors.

Uploaded an updated Beta version of SciTE zipfiles containing a fix for the lexer colors.

Uploaded an updated Beta version of SciTE zipfiles containing a fix for the lexer colors.

The issue is much simpler than what I initially though...  and my post was just to show how you can "simplify" the report of a bug as my example show the exact same issue as yours ...right?
I think that AutoIt3 simply "assumes" the start of a comment-block is a #directive line starts with "#cs" or "#comment-start", and ends the commentblock when a #directive line  starts with "#ce" or "#comment-end"... the rest is simply ignored. So i need to do the same in the lexer and color anything after the keywords as comment-bock.

Ok so Management summary:
#cs ;Example Correctly highlighted #ce #cs= ;Example Wrongly highlighted #ce Will have a look when I feel like opening that source again as I must say I lost the motivation to work on it as in general when I ask for something there's hardly any interest.  
An example that involves you:  Question asked and answered, with my follow-up without any response. 
(Not blaming, just explanation why I lost interest to work on anything dealing with SciTE4AutoIt3)
 

Understood and didn't need an explanation, just wanted to clarify that I feel there are only demands and a lack of support when I ask for people to test something.
This needs to be a 2-way street as far as I am concerned for me to stay motivation to spend time on it. 
So: Nothing personal towards you, just meant for the whole community when they want to look at me for New stuff or Support. 

Confirmed fixed. Thank you.

Ah...  This happens when you don't have VSCode installed.
Should be fixed in the current beta version of SciTEConfig.au3.
Thanks for reporting.

Alright, 1.8.3 is released with the fix!
FYI, I cannot upload my release to Open VSX, something seems to be going on with their servers (file upload giving HTTP status 500).
Open VSX works again, and 1.8.3 has been uploaded there also, now