AutoIt Extension for Visual Studio Code

[LoganCH]

On 10/11/2025 at 1:26 AM, jpm said:

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

You're supposed to be able to set #AutoIt3Wrapper_AU3Check_Parameters with the flags you want (which would be -w- 4 for turning off the local in global scope warning) but turns out there's a bug with reading them in for the diagnostics that I'm fixing right now.

`

[LoganCH]

Released v1.3.0!

 

Added

• COM object syntax highlighting for properties and methods using dot notation
• Distinct token scopes for COM identifiers (support.class.com.autoit) to enable theme-specific styling
• Contributors section to README.md with auto-updating contrib.rocks integration
• Added missing AutoIt macros: @exitMethod, @GUI_DropId, and @SW_ENABLE to completions and hovers
• AU3Check parameter parsing support with corresponding tests to improve syntax check behavior
• Parameter validation and improved status messages in OutputChannelManager (#230)
• WinNet API completions added to IntelliSense

Fixed

• Function pattern incorrectly matching COM object methods (e.g., $obj.Method() now correctly identified as COM, not function)
• Incorrect documentation for @GUI_CtrlId macro (now correctly states "Last click GUI Control identifier" instead of "Drag GUI Control identifier")
• Duplicate WinNet signature removed and WinAPI COM signatures added to signature/hover data
• Incorrect CRLF constant definition corrected
• Duplicate parameter documentation entries removed in signature help provider
• Removed stray duplicate (misspelled) Clibpoard completion entry
• Improved parameter checks in runCheckProcess for more reliable regex matching

Changed

• Consolidated macro data into single source of truth (src/completions/macrosData.js) to eliminate duplication and ensure consistency between completions and hovers
• Converted src/hovers/macros.json to src/hovers/macros.js to import from unified macro data source

Rate and View on VS Code Marketplace

Rate and View on OpenVSX

Star & Submit Issues on GitHub

[LoganCH]

Released v1.4.0!

Added

• Map variable IntelliSense - Intelligent key completions when accessing AutoIt Map variables
  • Shows available keys when typing a Map variable name (e.g., typing $map shows known keys)
  • Tracks Map keys across your workspace and included files
  • Works with both direct assignments ($map["key"] = value) and declarations with initial keys
  • Configuration options to tune behavior:
    • autoit.maps.enableIntelligence - Enable/disable Map intelligence (default: true)
    • autoit.maps.includeDepth - Maximum depth for resolving #include files (default: 3, range: 0-10)
    • autoit.maps.showFunctionKeys - Show Map keys assigned in functions (default: true)
  • See docs/map-support.md for performance tuning recommendations
• Scope-aware variable IntelliSense - Intelligent context-aware variable completions that respect AutoIt's scoping rules
  • Shows only accessible variables at cursor position (local, static, global, and parameters)
  • Prioritizes local variables over globals for better relevance
  • Respects function boundaries and AutoIt's scope rules (global and function-level scoping)
  • Extends to global variables from #include files
  • Intelligent debouncing (500ms) with concurrent update handling
  • Fallback to regex-based completion when service is unavailable
• Ignore AutoIt Tidy backup files from diagnostics

Fixed

• Improved error handling for variable tracking updates during configuration changes
• Enhanced stderr and process error handling in Au3Check execution

Changed

• Enhanced README documentation with Map intelligence feature details
• Enhanced variable parsing with support for comma-separated declarations (e.g., Global $a, $b, $c) and improved string handling for AutoIt's double-character escaping
• Extracted formatter constants into constants.js file
• Syntax Highlighting Improvements
  • Migrated syntax definition from XML to JSON format (autoit.tmLanguage.json) for better maintainability and IDE support
  • Enhanced function pattern matching to distinguish function declarations from function calls with dedicated scopes
  • Consolidated all 98+ AutoIt macros into dedicated pattern repository for improved consistency
  • Improved numeric constant parsing with better hexadecimal, decimal, and scientific notation matching
  • Refined operator patterns for comparison, assignment, arithmetic, and concatenation with proper precedence
  • Fixed multi-line string handling by refining string end patterns
  • Enhanced preprocessor directive matching (#include, #pragma, #region, etc.) for better accuracy
  • Improved comment block pattern matching (#comments-start/#cs directives)
  • Reorganized send-key patterns into 13 categorized groups (browser keys, media keys, navigation, numpad, lock, editing, system keys) for granular theme customization

 

Rate and View on VS Code Marketplace

Rate and View on OpenVSX

Star & Submit Issues on GitHub

[LoganCH]

Released v1.5.0!

Added

• VS Code variable support in path settings: settings that accept file paths (e.g. autoit.aiPath) now resolve VS Code variables such as ${workspaceFolder} and ${userHome} (#240) (29d494b)

Fixed

• Includes without trailing space now colorize correctly.
• Variable completions not appearing on startup: completions now initialize correctly during extension activation. The scope-aware path also falls back to regex-based completion when the parser returns empty results.
• Signature provider crashes on malformed input: dynamic regex fragments are now escaped in parameter and header documentation extraction, preventing crashes from malformed parameter or function names.
• Signature parsing errors: parameter and header documentation extraction now returns safe defaults instead of throwing on unexpected input.
• Smart-help errors with special characters: query text is now escaped before regex construction, preventing invalid regular expression errors.
• Go to Definition (F12) performance regression: introduced in v1.4.0 — three improvements that together restore lookup speed to parity with v1.1.0/v1.2.0
  • Simplified the variable-definition regex to eliminate backtracking on large files
  • Added a stat grace period to skip redundant filesystem checks on rapid repeated lookups
  • Added a per-document definition cache that is evicted on edit
• Function declaration parameter scopes: TextMate grammar now keeps the declaration scope active through the closing parenthesis and assigns a dedicated variable.parameter.autoit scope to parameters (965c5f6)
• Error handling in diagnostics and AI config: improved debug logging and error recovery in diagnosticUtils, ai_config, and extension activation paths (0d52962)
• Function parameter parsing with quoted parentheses: parser and TextMate grammar now correctly handle ) characters inside quoted strings in function default parameter values (#243) (40c727f)

Changed

• Separated some preprocesors to be colored closer to Scite.
  • Token scope (keyword.control.directives.autoit) now is used for Include-Once, NoTrayIcon, RequireAdmin and OnAutoItStartRegister
  • Token scope (meta.preprocessor.autoit) is used for all others.
• Improved regex patterns for #include directive resolution and function description matching in the utility module (640699a)

Removed

• Removed deprecated mainFunctions.js static AutoIt function completions file (1,645 lines); dynamic completions take over fully (fe8e176)
• Removed deprecated udf_WinAPITheme.js completions file (b5f2b6a)

 

Rate and View on VS Code Marketplace

Rate and View on OpenVSX

Star & Submit Issues on GitHub

[WildByDesign]

12 hours ago, LoganCH said:

Released v1.5.0!

I just wanted to give a quick Thank You for your continued work and efforts with this fantastic extension. I don't know what I would do without it.

Your time and efforts are greatly appreciated and you are very well organized. Thank you!

[ioa747]

Fix folding issue with single-line If statements

At first I thought about doing it as a PR, but I'm not familiar with your work (I use it occasionally.)
so I just thought I'd inform you here.

Spoiler

Title: Fix folding issue with single-line If statements

Description:

This PR fixes a bug where the code folding mechanism breaks when using single-line If...Then statements.

The Issue: The current increaseIndentPattern and folding.markers.start regex triggers a new folding block whenever it encounters the word If at the start of a line. In AutoIt, single-line If statements (e.g., If $condition Then $action) do not require an EndIf. Because the parser expects an EndIf that never comes, it incorrectly "swallows" all subsequent code, breaking #Region folding and indentation for the rest of the script.

The Solution: Updated the regex for If to ensure it only initiates a folding block when the Then keyword is at the end of the line (optionally followed by a comment). If there is any code following the Then keyword on the same line, it is correctly identified as a single-line statement and ignored by the folding logic.

Changed Regex: From: ([iI]f\\b) To: (?i:If)\\s+.*\\s+Then(?:\\s*;.*)?$ (or the equivalent string escaped for JSON)

in the file autoit-language-configuration.json

from:

"folding": {
    "offSide": true,
    "markers": {
      "start": "^\\s*\\s*((#?[Rr]egion\\b)|([Ff]unc\\b)|([iI]f\\b)|([sS]witch\\b)|([fF]or\\b)|([wW]hile\\b)|([wW]ith\\b)|(#c(?:omments\\-start|s)))\\b",
      "end": "^\\s*\\s*((#?[Ee]nd[Rr]egion\\b)|([Ee]nd[Ff]unc)|([eE]nd[iI]f)|([eE]nd[sS]witch)|([nN]ext)|([wW][eE]nd)|([eE]nd[wW]ith)|(#c(?:omments\\-end|e)))\\b"
    }
  },

to:

"folding": {
    "offSide": true,
    "markers": {
      "start": "^\\s*(?:#?[Rr]egion\\b|[Ff]unc\\b|(?i:If)\\s+.*\\s+Then(?:\\s*;.*)?$|[sS]witch\\b|[fF]or\\b|[wW]hile\\b|[wW]ith\\b|#(?:comments-start|cs))",
      "end": "^\\s*(?:#?[Ee]nd[Rr]egion\\b|[Ee]nd[Ff]unc|[eE]nd[iI]f|[eE]nd[sS]witch|[nN]ext|[wW][eE]nd|[eE]nd[wW]ith|#(?:comments-end|ce))"
    }
  },

 

 

[donnyh13]

Very nice ioa747,

6 minutes ago, ioa747 said:

Fix folding issue with single-line If statements

I tried to do a similar task too once, but I found that continued "If"s would cause issues.

if (1= 1) And _
(2 = 2) Then