Search the Community

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. 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). Locate your VS Code extensions folder, mine was found at the following location: C:\Users\Owner\.vscode\extensions 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. Open Logan's extension folder found in the VS Code extension folder (not the copy you made). 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

So another vscode extension for the AutoIt language emerges! I've tried the existing ones, and found small problems that i felt i could improve on, but it would require an entire new approach to the inner working of the existing extensions. Also working on a complete AutoIt3 parser a vscode extension just made sense Any feedback is appreciated, and i hope this project will benefit more than just me 🤡 Visual Studio Code Marketplace GitHub repo Some of the current features: Basic AutoIt2 syntax highlighting, for fun 🤡 AutoIt3 syntax highlighting Variable/Function hover gives declaration information if available. Goto declaration #include links Syntax checking, as you type Function signature help Function and variable list in a file via the outline tab. Works on desktop (any OS) and web version ⚠️ The parser used is not yet 100% complete (see issues for know problems), and the last thing to be implemented is the With code block. Hope you like 😃

I use Autoit plagin from Damien in VS Code When I press Shift + Alt + F I got message: There is no formatter for autoit And there is no extention when I searh category:formatters autoit

When I press F5 in VS Code for Autoit code, the script is restarted and all logs from the bottom OUTPUT console disappear Prohibiting the launch of only one copy of the script does not help, still in OUTPUT are written logs for a new attempt to run, and the old running script disappears, although it continues to run. Is it possible to return to the logs of the first running script so that it also writes everything it does in OUTPUT ?

Have downloaded and installed AutoIt and AutoIt Script Editor also I installed plugin AutoIt Damien I can run scripts by pressing the F5 But If I try Run->Run Without Debugging or Run->Start Debugging I have an error You don't have an extension for debugging autoit How I can fix this or how can I run the autoit from the VS code menu ?

Hi folks, personally, I felt it always unclean or simply ugly to include whole UDFs into his script or project, in cases where you need only individual functions from it. The fact that the *.exe gets larger when compiling is often no longer a problem these days or you just don't mind it anymore - I, on the other hand, do somehow 😅 . That's why I used to take the individual functions from the UDFs into my script so that I didn't have to include the entire UDF (#include). Depending on the license, I have recorded the attribution of the UDF creators or the contributors in the credits or similar to keep it fair. Then the change came: I got to know Visual Studio Code (VSCode) professionally, first for other languages, then also for AutoIt. With VSCode's rapidly improving and nowadays very powerful IntelliSense (code completion) I got an idea. Easy and fast: I store functions that I often need or have in some (own) UDFs in snippet files and can quickly insert them into the respective script or project if required. But it's important to me that I can access the functions contained in the snippets from anywhere - on my private computer, at work or at a colleague's/friend's. So I created a VSCode Extension 😀 . VSCode-AutoItSnippets: If you also implement your AutoIt projects with VSCode, then my AutoIt Snippets Extension might interest you or even help you to implement your projects faster. I would be very happy if you could take a look at the project. Of course, I'm interested in your opinion on this as well as whether one or the other would like to share their function(s) and would also like to have them immortalized in the extension 🧐 . If this should be interesting for you, then you are welcome to add your functions via pull request, or just write them here so I can include them in the snippet files, or you write with a private message or email. I'm curious if this can be helpful for you, because there are already over 500 installations of the extension, which makes me happy 😁 . This is how it looks in practice/in use: https://github.com/Sven-Seyfert/VSCode-AutoItSnippets#features Best regards Sven ________________ Stay innovative!