AutoIt Extension for Visual Studio Code

[jaberwacky]

Hello lovely people. I installed Autoit3 and VSCode and installed Damien's extension. When I ran a script then I would see the errors and warnings neatly output to the console. However when I installed Scite4AutoIt3 then I no longer get the problems in the console. Anyone know how to change this?

[jaberwacky]

Nvm, I was looking at it wrong. Sorry!

[LoganCH]

Added

• File path validation to prevent path traversal attacks

• Parameter safety warnings for autoit.consoleParams to detect potentially dangerous shell metacharacters

• Workspace symbol performance optimizations with batch processing to prevent UI freezing on large projects

• Configuration options autoit.workspaceSymbolMaxFiles (default: 500) and autoit.workspaceSymbolBatchSize (default: 10)

• Configuration option autoit.symbolMaxLines (default: 50000) to control maximum lines processed for symbol information

• Warning message when files exceed symbol processing limit with actionable instructions

• Comprehensive unit tests for completion provider with 8 test cases

• Comprehensive README documentation improvements with installation guide, quick start section, platform support matrix, troubleshooting guide, and reorganized configuration

• Distribution scripts for packaging the extension to multiple marketplaces:

  • package-all.js for simultaneous packaging to VS Code Marketplace and OpenVSX

  • package-openvsx.js for OpenVSX-specific packaging with publisher name handling

Fixed

• Command injection risk in registry update functionality by replacing exec with execFile for safer argument handling

• Multiple global output panels opening for AutoIt on startup

• Memory leak in completion provider where include cache grew indefinitely across document switches

• Incorrect array comparison logic in completion cache invalidation

• Cross-document contamination of completion items from include files

Changed

• Simplified ESLint configuration by using globals package and removing redundant rules

• Workspace symbol cache now uses incremental updates instead of full invalidation on file changes

• Completion provider now uses per-document Map-based caching with LRU eviction (50 document limit)

• Include cache automatically cleans up when documents are closed

• Symbol processing limit increased from hardcoded 10,000 to configurable 50,000 lines by default

Removed

• The unused autoit.YAML-tmLanguage file

 

Rate and View on VS Code Marketplace

Star & Submit Issues on GitHub

[jpm]

I try to use VS_code keeping Scite as the default editor

I found out that i need to trust the folder where the file is located

My question is : is it needed to trust the folder before using the extension?

Thanks to help me with this new environment for a old scite user !!!

Cheers

[jpm]

Is there a way to suppress the Local warning on the a main script

[mLipok]

Normally I would use directives:

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w 5 -w 6 -w 7

instead

#AutoIt3Wrapper_Au3Check_Parameters=-d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6 -w 7

just omnit

-w 4

parameter

But how to do this with VSC ? do not know

Edited October 11 by mLipok

[jpm]

no that's my question

Edited October 12 by jpm

[jpm]

What to do to have @ displayed 

[jpm]

Is it possible to Have the Ctrl-Q which comment/uncomment line(s) as Scite does?

edited: I see Ctrl-: does 

can i change it to Ctrl-Q?

Edited October 12 by jpm

[jpm]

I notice the F7 does not produce any Output line

is it a way to have it working?

[jpm]

Is it normal that the comments lines are not process same way as Scite/tidy?

[jpm]

Will F1 open the autoIt help corresponding to info in AutoIT.chm ?

[donnyh13]

8 hours ago, jpm said:

Is it normal that the comments lines are not process same way as Scite/tidy?

If you mean after running tidy, Jos changed the behaviour I believe, because the un-indented line was breaking VSC folding.

On 3/8/2025 at 11:52 AM, Jos said:

I had one "annoyance" while using VSC where Ctrl+/ does what in SciTE is accomplished with Ctrl+Q, but in SciTE the :~ is added at the start of the line and in VSCode it is added indented in front of the code with one space. Then when tidy is ran, the comment is moved to the left as Tidy assumes that SciTE requires it to be at the start of the line.
Is there any reason why VSCode works different, or do people like it better that way? 
I can change Tidy in a way that when ran by Scite, it does the current behavior and when run by other editors it will Indent the comments with the normal code.

 

On 3/9/2025 at 8:17 AM, Jos said:

On 3/8/2025 at 12:45 PM, genius257 said:

Generally respecting the indentation when commenting or un-commentating a line seems like the best approach in my opinion. Doing it like in SciTE, gives issues, when you want to indent a section containing an out-commented line of code, where with vscode the identation is no issue and un-commentating the line later, does not produce the same possible problems.

No issue, so we would want Tidy to respect that when not ran from SciTE.  I have uploaded a Beta version that checks how the program is shelled and will Indent linecomments when not ran from SciTE.

On 3/10/2025 at 6:04 AM, Jos said:

*** Updated Tidy v25.205.1420.x (Jos)
   - 25.205.1420.1 Change Indentation of linecomments to indent the same as the other lines, when not ran from SciTE.

 

8 hours ago, jpm said:

can i change it to Ctrl-Q?

If you press the gear icon in the bottom left of VSC, then click "Keyboard shortcuts", OR press ctrl+k ctrl+s to open "Keyboard shortcuts", then in the search bar at the top, search for "comment", and look for "Toggle Line Comment". Hover that, and click the pencil icon on the left of the line to set it as desired.

  

8 hours ago, jpm said:

Will F1 open the autoIt help corresponding to info in AutoIT.chm ?

Quote

Launch AutoIt tools directly from VSCode:

• AutoIt3 Help (Ctrl+F1)

Ctrl+f1 will.

Edited October 12 by donnyh13

[jpm]

Quote

If you press the gear icon in the bottom left of VSC, then click "Keyboard shortcuts", OR press ctrl+k ctrl+s to open "Keyboard shortcuts", then in the search bar at the top, search for "comment", and look for "Toggle Line Comment". Hover that, and click the pencil icon on the left of the line to set it as desired.

it is conflicting with workbench

perhaps a autoi:!Toogle comment line is needed

Thanks

 

[jpm]

Quote

Launch AutoIt tools directly from VSCode:

• AutoIt3 Help (Ctrl+F1)

I understand that F1 is use by VSCode

does a Autoit:help using F1 is  solution

[jpm]

I try to follow the discussion about indenting th e comment line

Bot sure what is the final solution

[jpm]

Quote

What to do to have @ displayed 

Is there a solution

[jpm]

Quote

i notice the F7 does not produce any Output line

is there a solution?

[jpm]

Thanks @donnyh13 for all your feedback

😀

[SOLVE-SMART]

Unfortunately, I cannot answer in detail right now, but there are answers and explanations to your questions @jpm.

The current version of the extension has a bug regarding output. Keyboard shortcuts, just like in the SciTE layout, are all customizable. The file encoding (codepage) can be set (reset) to display the @ sign correctly. This could happen, if you wrote your script in SciTE and use it now in VSCode. Once reset to UTF-8, it should be displayed correctly in both editors.

I am on vacation at the moment. When I am back, I can provide several screenshots for all the questions 🤝 .

Best regards

Sven