Scite4AutoIt Themes for VS Code

[donnyh13]

Greetings AutoIt community;

I’m not sure if there is much need nor desire for this little project, but I thought I would share it in case there is.

These themes are an attempt to copy over the themes that come with Scite4AutoIt. Being that there are many further customizations available for VS Code compared to Scite, many colorations in VS Code may not match, and these may not be as well combined as they are in Scite, as VS Code colorizes things slightly different from Scite in some instances.

Because of the vast number of available settings and tokens for each language, it has been thought best to only have these custom themes apply to AutoIt files. I have used the token names from the two leading AutoIt extensions that are currently available, published by LoganCH and Genius257, consequently, if neither is installed or activated AutoIt syntax highlighting will be defaulted to VS code colorings. When the user opens any other language file, the theme coloring will revert to the base theme's colorization for tokens (see Read-Me chart), but the editor colors (background, similar word highlight, etc.) will not.

The vsix file can be downloaded from the following, as I do not intend to publish these on the marketplace: https://github.com/donnyh13/Scite4AutoIt_Themes/releases

The base themes are three themes included with VS Code: VS Code Light, VS Code Dark, and Monokai, which are all MIT licensed, and belong to the respective owner(s). Copyright (c) Microsoft Corporation.

All Scite Themes, colorings and names are owned by the developers of Scite4AutoIt, and the respective theme creators, and I claim no ownership to any of them.

If any of the theme owners wish for these to be removed, please let me know.

Note

For those users on older Windows versions, and unable to update VS Code to later versions, the following should be noted. The extension created by LoganCH became incompatible from version 1.0.14+ with Vs Code 1.70.3, (the latest available on Windows 7). In Logan's versions 1.4.0, and 1.5.0 there were several modifications and additions that make tokenization better, and cleaner, which users on older systems will not be able to benefit from. As a possible work around, see below.

As of the time of writing (May, 2026), Genius257's extension (v1.8.9) is still compatible with VS Code 1.70.3, and does not present these issues.

Possible Workaround

Being under the above limitations myself, I have found the following workaround. Any users with some coding experience can follow the following steps at their own risk. These directions work for Logan's version 1.5.0. I make no guarantee it will work with later versions.

1.  Download a copy of Logan's extension files from his GitHub, or, minimally, a copy of the file autoit.tmLanguage.json, found in the syntaxes file. (Make sure to get the file with the .json extension).
2. Locate your VS Code extensions folder, mine was found at the following location:
    C:\Users\Owner\.vscode\extensions
3. Make a copy of Logan's extension folder somewhere else, in case something goes wrong. The extension folder is named: damien.autoit-1.0.13 or similar.
4. Open Logan's extension folder found in the VS Code extension folder (not the copy you made).
5. Find and open the package.json file.

• 5.1. Inside the package.json file, find the following line, (Mine was around line 225):

"grammars": [
            {
                "language": "autoit",
                "scopeName": "source.autoit",
                "path": "./syntaxes/autoit.tmLanguage"
            },
            {
                "language": "vscode-autoit-output",
                "scopeName": "source.vscode_autoit_output",
                "path": "syntaxes/vscode-autoit-output.tmLanguage.json"
            }
        ],

 

• 5.2. Edit the "path" line for "language": "autoit"
• From:

"path": "./syntaxes/autoit.tmLanguage"

• To:

"path": "./syntaxes/autoit.tmLanguage.json"

• 5.3. Save and close the file.

6. Navigate to inside the Syntaxes folder.

7. Copy the new autoit.tmLanguage.json file into this folder, replacing the existing file, if present.

8. Close VS Code if open, and open an AutoIt Script in VS Code to make sure everything is colorized properly, and that no errors are present.

 

Previews

Standard

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Standard.png

Old-Standard

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Old Standard.png

Old-LCD

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Old LCD.png

MSDEV

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/MSDEV.png

MSDEV2

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/MSDEV2.png

Dark

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Dark.png

Monokai

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Monokai.png

Twilight

https://github.com/donnyh13/Scite4AutoIt_Themes/blob/main/img/Previews/Twilight.png