AutoIt Extension for Visual Studio Code

[HurleyShanabarger]

Love that release! Thank for the work ♥️

[LoganCH]

23 hours ago, Danp2 said:

I don't believe that I had anything to do with this one. If I turn out to be wrong, then I will just chalk it up to my sometimers disease. 🤪

You're right, it was vanowm, my fault.

Edited December 2, 2022 by LoganCH
meant "it" not "I"

[LoganCH]

Released v1.0.12 today, here's what changed:

Added

• Signature help pulls description and parameters from function headers
• Option to disable `(` as an option to accept function completion suggestions
• Syntax highlighting for `#Tidy_On`, `#Tidy_Off`, and `#Tidy_ILC_Pos` directives

Changed

• Path checks for utility executables (e.g., Au3Check) reduced to occur when changes are made and disabled for non-Windows OSes
• Simplified regex for functions
• Trimmed spaces in insertHeader command
• Removed default configuration settings that were overriding user settings

Fixed

• Open include shortcut not working for library UDFs
• Open include shortcut not working for paths with `#` in them
• Function autocomplete from include files
• Reduced completion suggestions when writing function definitions

Contributors

@vanowm, @rcmaehl

 

View and Rate on VSCode Marketplace

View and Rate on Open VSX Registry

Star, Submit Issues, and Contribute on GitHub

[Enchillada411]

One question regarding the VS Code extension AutoIT v1.0.12 (Damien)...

Is it possible to see function documentation / header of customer functions?

Means, the same way when I hover cursor on function call of homebrew functions, like it is done when I call a standard AutoIt function?

I have seen this in other AutoIT extensions, supporting DocBook.

[Enchillada411]

20 hours ago, Enchillada411 said:

One question regarding the VS Code extension AutoIT v1.0.12 (Damien)...

Is it possible to see function documentation / header of customer functions?

Means, the same way when I hover cursor on function call of homebrew functions, like it is done when I call a standard AutoIt function?

I have seen this in other AutoIT extensions, supporting DocBook.

Ok -  I see.

This feature is already requested

Implement hovers for user-created functions & variables · Issue #201 · loganch/AutoIt-VSCode · GitHub

[LoganCH]

Released v1.0.13 today!

Added

• Command to remove Debug to Console and MsgBox lines added by the extension

• Commands to add and remove debug Trace lines

• Refined syntax check, with ability to set options through #AutoIt3Wrapper_AU3Check_Parameters

• Completions and Hovers for AutoIt3Wrapper Directives

Changed

• Changes to autoit.includePaths setting now gets written to Windows Registry

Fixed

• Go To Definition regression

• Output colors not showing due to other extensions (e.g., Github Copilot)

• Icons missing for some Const and Enum variables in the outline/Symbol search

• Detection of nested Regions

• outputCodePage setting not working

• Au3Check/Problems tab now works with includePaths setting

Contributors

@Danp2, @vanowm, @Sunev

View and Rate on VSCode Marketplace

Star, Submit Issues, and Contribute on GitHub

[SOLVE-SMART]

Thank you @LoganCH 👌 .

I guess you plan to create a GitHub release too, right?
In my VSCode your newest version is loaded just fine (automatically), but on your GitHub repo the latest Release is still the "old" one.

Best regards
Sven

[LoganCH]

On 1/29/2025 at 1:37 AM, SOLVE-SMART said:

Thank you @LoganCH 👌 .

I guess you plan to create a GitHub release too, right?
In my VSCode your newest version is loaded just fine (automatically), but on your GitHub repo the latest Release is still the "old" one.

Best regards
Sven

Yeah, I wrote up the whole draft but had forgotten to make it final.

[LoganCH]

Released v1.0.14 today!

Changed

• Node package update.
• Sets editor.minimap.showRegionSectionHeaders to false for AutoIt scripts.
• Optimized editor command registrations.
• Enhancements to syntax definition file.

Fixed

• Usage of wrong Au3Check encoding for the file path string.

View and Rate on VSCode Marketplace

View and Rate on OpenVSX

Star, Submit Issues, and Contribute on GitHub

[LoganCH]

Released v1.1.0 yesterday!

Added

• Support for running the Format Document command via the Command Palette or hotkey using Tidy.exe on scripts, including automatic formatting on save

• Jest testing framework with test suite for language features and services

Changed

• Refactored monolithic command code

• Upgraded build toolchain

• Diagnostic system overhaul with encoding handling and problem script source tracking

Fixed

• Restored Go to Definition functionality for symbols declared outside of current script

• Restored Open Include file (Alt+i) functionality

• Path handling improvements

• Completion provider accuracy with user-defined functions

View and Rate on VSCode Marketplace

View and Rate on OpenVSX

Star, Submit Issues, and Contribute on GitHub

[donnyh13]

  Hi Logan, or to whom it may concern;

I didn't see anything mentioned in the release notes, but it would seem that as of version 1.0.14+, this extension isn't compatible with VSC 1.70.3 (and thus Windows 7 (1.70.3 seems to be the last version to support Windows 7)). Would that make sense? I get the following when trying to manually install the vsix.

Quote

Unable to install extension 'damien.autoit' as it is not compatible with VS Code '1.70.3'.

Thanks for all of your work.

Best regards,

Edited Tuesday at 07:52 PM by donnyh13

[SOLVE-SMART]

Hi @donnyh13 👋 ,

could you please provide more information about your VSCode?
Simply open the command palatte and type: "> Help: About".

For example my current version on Win10 is:

Version: 1.104.2 (user setup)
Commit: e3a5acfb517a443235981655413d566533107e92
Date: 2025-09-24T11:21:37.073Z
Electron: 37.3.1
ElectronBuildId: 12404162
Chromium: 138.0.7204.235
Node.js: 22.18.0
V8: 13.8.258.31-electron.0
OS: Windows_NT x64 10.0.19045

 

1 hour ago, donnyh13 said:

[...] this extension isn't compatible with VSC 1.70.3 (and thus Windows 7 (1.70.3 seems to be the last version to support Windows 7)). Would that make sense?

I think so, yes. To you really want to stick with Win7 or you're talking about a VM?
I strongly believe the VSCode AutoIt Extension will not the only one which will lead to problems on such a old system, right 😅 .

Best regards
Sven

[donnyh13]

2 hours ago, SOLVE-SMART said:

could you please provide more information

Quote

Version: 1.70.3 (user setup)
Commit: a21a160d630530476218b85db95b0fd2a8cd1230
Date: 2022-08-31T08:03:55.990Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 6.1.7601

 

2 hours ago, SOLVE-SMART said:

I strongly believe the VSCode AutoIt Extension

Yes, I believe so too. I like it for working on. It's predictable and works well for me, so I stick with it. It's nothing important, I just wanted to confirm that it really isn't compatible anymore, and not just a bug on my end. I am getting used to stuff getting advanced past working on W7. One day, it will get retired I suppose .

Thanks for the help @SOLVE-SMART. Much appreciated.

Edited Tuesday at 11:20 PM by donnyh13

[SOLVE-SMART]

7 hours ago, donnyh13 said:

I like it for working on. It's predictable and works well for me, so I stick with it.

Understood, thanks.

7 hours ago, donnyh13 said:

I just wanted to confirm that it really isn't compatible anymore, and not just a bug on my end.

Alright. I cannot reproduce it, because I don't use Win7 anymore and I also don't want to setup a VM for it.
But maybe @argumentum wants to check it on a Win7 machine. I say so, because I believe you (argumentum) often works with VMs and maybe already have a Win7 one processed?

Besides that, I think more and more extensions will or already have ended the support for Win7, because it's might be more a matter of the Node.js runtime in the background for VSCode. Anyway, interesting finding - it is surely documented in the VSCode release notes anywhere (I think).

--------------

Kind of off-topic, but important anyway:

Spoiler

7 hours ago, donnyh13 said:

Thanks for the help @SOLVE-SMART. Much appreciated.

I didn't much 😇 . But I appreciate your (and some other peoples) polite communication structure above several threads here. Nice to see (read) that questions and answers can be respected and be valued 👌 . There's a German saying: "ein geben und nehmen" (a give and take), which, among other things, stands for such good behavior.

Best regards
Sven

Edited 18 hours ago by SOLVE-SMART

[argumentum]

8 hours ago, SOLVE-SMART said:

Alright. I cannot reproduce it, because I don't use Win7 anymore and I also don't want to setup a VM for it.
But maybe @argumentum wants to check it on a Win7 machine. ...

I could install Win7 in a VM but am clueless to all VSCode. I don't use it. Would not know what works and what don't.
If you don't have a Win7 ISO, go to torrent-land and get an up to date one.

15 hours ago, donnyh13 said:

I just wanted to confirm that it really isn't compatible anymore, and not just a bug on my end. I am getting used to stuff getting advanced past working on W7. One day, it will get retired I suppose .

I'll retire the day I die. Maybe even after !

I loved WinXP but time moves forward. Win11 ain't bad ( after you tweak the heck out of it ).
I install Windows on any language is not because am a polyglot, but because everything is always pretty much the same in the same place, same icons.

Remember: Your feet don't stay on the ground because of gravity. The whole planet stick to your feet because of your gravitas 🙇

[SOLVE-SMART]

12 minutes ago, argumentum said:

I could install Win7 in a VM but am clueless to all VSCode. I don't use it. Would not know what works and what don't.

Fair enough, understood, thanks.

12 minutes ago, argumentum said:

If you don't have a Win7 ISO, go to torrent-land and get an up to date one.

Thanks 👌 .

13 minutes ago, argumentum said:

I'll retire the day I die. Maybe even after !

😂

13 minutes ago, argumentum said:

Remember: Your feet don't stay on the ground because of gravity. The whole planet stick to your feet because of your gravitas 🙇

Maybe you should rename yourself to Philosoph'tum 😆 .

Best regards
Sven

[donnyh13]

9 hours ago, SOLVE-SMART said:

might be more a matter of the Node.js runtime in the background for VSCode

Thanks for the reply and the diagnostics. Yes, I bet you are correct. Looking at Logan’s release notes for the version that is no longer compatible, node.js is the only thing there that would make sense as being the problem.

50 minutes ago, argumentum said:

Remember:

35 minutes ago, SOLVE-SMART said:

Maybe you should rename yourself to Philosoph'tum 😆 .

😂 I think this would be fitting!

Thanks everyone for the help.

off-topic reply-------------------

Spoiler

9 hours ago, SOLVE-SMART said:

But I appreciate your (and some other peoples) polite communication structure above several threads here.

Yes, I too appreciate that discussions on here can be kept polite and respectful to one another. It accomplishes so much more that way. Thanks for that interesting German proverb. It reminds me of the Biblical rule that I try to follow, which goes essentially like this: “Treat others how you would like to be treated if you were in their position.”

Best regards,