BETA: SciTE v5x & lua Dynamic_include and "Smart" AutoComplete for Vars/UDFs/Abbrevs

[BinaryBrother]

Woah. That would be an idea. I use VSCode and Github Copilot all the time.

Edit: Well holy shit, some people have it working and it even works with the shadow suggestions.

F5 Actually ran and returned console. I'm going to experiment with VSCode for a while, I hadn't realized that was an option.

https://app.screencast.com/URbDfl7s3Vdei

I like it! Thanks for the recommendation!

Edit: I forgot about Tidy... Maybe the way they "Format Document" will be good enough.

Edit: Check this out... CoPilot is making recommendations for my UDF to meet UDF-Spec.

https://app.screencast.com/cIO6jNdUM6mVi

Warning, though... It doesn't fully understand AutoIt but does a pretty good job of interpreting certain things. At least I can use it for header generation.

Last Edit: Gotta watch the Copilot with your code, though. It messed up some of my functions while adding the headers.

Edited January 29 by BinaryBrother

[Jos]

On 12/18/2024 at 8:14 PM, Jos said:

Just uploaded SciTEx86.zip & SciTEx64.zip which contain the Latest SciTE 5.5.4 versions released today 18 December 2024.

Updated SciTE:

• Fixed UTF8 BOM detection.

[Jos]

I am getting ready to publish a production update for SciTE4AutoI3, so have a SciTE4AutoIt3 v25.205.1420.0 release candidate ready and uploaded to Beta for those willing to test this installer before releasing it. Would appreciate hearing whether there are still issues with it as it has been a major overhaul since the last production version back in 2021.  
My main drives at this moment are to get the setup ready for better supporting Visual Studio Code as the default editor for AutoIt3, as I am convinced that there is an added benefit using VSC over SciTE. I have no intent to drop the SciTE upgrades, but do prefer to stop development & support of all the written LUA script functionalities.

This is a list of the current changes at a high level:

• SciTE updated from v4.4.6 to v5.5.4 and includes both the x86 and x64 version selectable at install time
• Include the major LUA changes for Dynamic add Variables & Functions & #Include functionality. See here for details.
  • This can be Simply disabled when old behavior is preferred by settings dynamic.include=n
• Utilities (Tidy.exe/au3Stripper/Au3check) can now process mixed encoded files and special characters in the filenames, so they do not require AutoIt3Wrappper anymore.
• The Included au3check v3.3.17.1 is an update of the standard latest au3check v3.3.16.1 included in the AutoIt3 installer.
  The new au3check now also supports mixed encoded files and special characters in the filenames and can be used without AutoIt3Wrapper for those cases.
  The installer will check the current version and replace it with this version when it is < v3.3.17.1.
  A copy of the old version will be made to AutoIt3\SciTE\Au3Check
• The installer will prompt for 
  • SciTE.exe x86 or x64 version
  • Whether you want to change to VSCode as your default Editor for the "Edit" & "Open" options for AU3 files.
  • What to do with Double Click, either Open or Run with AutoIt3. (also an option to change in SciTE Config)

 

For those few that are currently using the Dynamic Beta version:

There are a few minor changes since the last version published:

• AutoComplete #include lines wasn't working when dynamic.include=n was set.
• I have added the option to limited the number of entries shown in the AutoComplete dropdown to make it much more responsive when e.g. typing $a :

  # Define the max entries is a Variable/Func dropdown autocomplete list for speed reasons.
  autocomplete_dropdown_max=200

   

Edited February 6 by Jos

[BinaryBrother]

I'll give it a spin...

Results:

I have VS Code installed, but it isn't detected.

[Jos]

12 minutes ago, BinaryBrother said:

I have VS Code installed, but it isn't detected.

I guess I was sort of expecting this to happen. Have you maybe installed VSCode for all users?

Could you check the existence of these registry keys? :

• HKCU\Software\Classes\Applications\Code.exe\shell\open\command"   (This is the one currently checked)
• HKLM\Software\Classes\Applications\Code.exe\shell\open\command"

I need the appropriate registry key for VSCode that you have for the Open command.

EDIT: Do you have this key, as that seems to be a standard one?:
 

Computer\HKEY_CLASSES_ROOT\*\shell\VSCode\command

Download and try the current version of the installer that contain the check for this last regkey and see if that works.

Edited February 6 by Jos

[SOLVE-SMART]

2 minutes ago, Jos said:

HKCU\Software\Classes\Applications\Code.exe\shell\open\command"   (This is the one currently checked)

This one 👆 matches my installation path (*current_user).

Best regards
Sven

[BinaryBrother]

HKCU\Software\Classes\Applications\Code.exe\shell\open\command FOUND

 

HKLM\Software\Classes\Applications\Code.exe\shell\open\command NOT FOUND

 

I think you have it backwards... Your Scite install must be checking HKLM, but VSCode is found under HKCU. At least, with @SOLVE-SMART and I.

Edited February 6 by BinaryBrother

[Jos]

Does this key exist in your registry?: HKCR\Directory\shell\vscode\command 

Edited February 6 by Jos

[BinaryBrother]

1 minute ago, Jos said:

Does this key exist in your registry?: HKCR\Directory\shell\vscode\command 

Negative. I don't have the vscode key.

[Jos]

How did you install VSCode? 
The regular VSCode installer as the last listed regkey is created by that installer.

Also the key that you show is the exact one I was using before while you say it didn't work?

Edited February 6 by Jos

[BinaryBrother]

I just grabbed it from the site https://code.visualstudio.com/

https://vscode.download.prss.microsoft.com/dbazure/download/stable/33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/VSCodeUserSetup-x64-1.97.0.exe

and installed it normally. I'm going to rerun the installer.

Edited February 6 by BinaryBrother

[SOLVE-SMART]

4 minutes ago, Jos said:

Does this key exist in your registry?: HKCR\Directory\shell\vscode\command 

Yes it does.

And I also do not get "Visual Studio Code not detected.", it's shown like in @Jos screenshot of post here.
In other words, works fine for me @BinaryBrother.

1 minute ago, BinaryBrother said:

I'm going to rerun the installer.

Good idea 👌 .

Best regards
Sven

[Jos]

1 minute ago, BinaryBrother said:

I just grabbed it from

https://vscode.download.prss.microsoft.com/dbazure/download/stable/33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/VSCodeUserSetup-x64-1.97.0.exe

and installed it normally. I'm going to rerun the installer.

Hang on ...   as you are showing the proper key  here:

 

14 minutes ago, BinaryBrother said:

HKCU\Software\Classes\Applications\Code.exe\shell\open\command FOUND

 

[BinaryBrother]

*shrug*. The HKCR\Directory\shell\vscode still does not exist for me.

I just re-ran the installer and used defaults.

I didn't opt for the two "Open with" checkboxes... I have a lot of drama in my context menus already, so I didn't want any more options. lol

Edited February 6 by BinaryBrother

[Jos]

Just uploaded an changed installer testing for both these keys and it should work when either one exists:

 

ReadRegStr $R0 HKCR "*\shell\VSCode\command" ""

ReadRegStr $R0 HKCU "Software\Classes\Applications\Code.exe\shell\open\command" ""

... but as I said: With the screen capture you shown it should have worked as long as you run the installer with your own userid.

Edited February 6 by Jos

[Jos]

9 minutes ago, BinaryBrother said:

I didn't opt for the two "Open with" checkboxes... I have a lot of drama in my context menus already, so I didn't want any more options. lol

Ok, that explains the generic key not existing!:

ReadRegStr $R0 HKCR "*\shell\VSCode\command" ""

... but the other one should still exist during installer run as long as it is ran by the same user as this is a "per user" installation.

[BinaryBrother]

My VSCode is installed in the user context. Your new ScITE installer requests Admin privs before running. I'm not sure if that's relevant or not.

Did you update the installer?

[Jos]

7 minutes ago, BinaryBrother said:

Did you update the installer?

yes:

23 minutes ago, Jos said:

ust uploaded an changed installer testing for both these keys and it should work when either one exists:

 

ReadRegStr $R0 HKCR "*\shell\VSCode\command" ""

ReadRegStr $R0 HKCU "Software\Classes\Applications\Code.exe\shell\open\command" ""

.

15 minutes ago, Jos said:

... but the other one should still exist during installer run as long as it is ran by the same user as this is a "per user" installation.

 

7 minutes ago, BinaryBrother said:

My VSCode is installed in the user context. Your new ScITE installer requests Admin privs before running. I'm not sure if that's relevant or not.

Correct and I do the same, and it prompts for Admin rights  (UAC) for me as well, but I don't have that issue, but my account is part of the Admin group.
Is your username on your computer part of the Administrators group or is it a restricted user only part of the users group?

Can you share your install.log from the SciTE directory?

Edited February 6 by Jos

[BinaryBrother]

It's a relatively fresh install of Windows 11 24H2, one primary administrative account. I haven't messed with ACLs, groups, or permissions.

I would assume that I'm in the admin group, since I can carry out administrative operations.

What is the fastest way to check? It's been a while since I messed with groups outside Linux.

Edit: I just re-downloaded the ScITE install from your link and tried again. It still doesn't detect my VSCode install.

I'll re-download it from a different browser to make sure caching isn't an issue.

It still doesn't work for me. 😕

I bet if I ticked those check boxes on the VSCode Installer it would. X) - It still didn't work. I'll try it on a fresh Win11 VM and see what happens.

I tried it in a fresh Win11 24H2 VM and it worked as expected. There must be something off about my setup... I have no idea what's going on, but the issue that I'm having appears to be a fluke relevant only to my particular setup and install.

Edited February 6 by BinaryBrother

[BinaryBrother]

23 minutes ago, Jos said:

Can you share your install.log from the SciTE directory?

 

install.log