<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs.tlapl.us/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://docs.tlapl.us/feed.php">
        <title>TLA+ Wiki - using:vscode</title>
        <description></description>
        <link>https://docs.tlapl.us/</link>
        <image rdf:resource="https://docs.tlapl.us/_media/logo.png" />
       <dc:date>2026-05-23T21:45:47+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:automatic_module_parsing?rev=1762248279&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:boxed_comments?rev=1729369410&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:caveats?rev=1729364150&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:commands?rev=1729364164&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:fonts?rev=1729365689&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:formatting_preferences?rev=1729364593&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:getting_started?rev=1758132021&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:installing_java?rev=1729875489&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:java_options?rev=1729365781&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:keyboard_shortcuts?rev=1729369471&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:migrating_from_tlatoolbox?rev=1760128798&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:settings?rev=1762248560&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:start?rev=1748731302&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:troubleshooting?rev=1729364389&amp;do=diff"/>
                <rdf:li rdf:resource="https://docs.tlapl.us/using:vscode:visualizing_states?rev=1729369348&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://docs.tlapl.us/_media/logo.png">
        <title>TLA+ Wiki</title>
        <link>https://docs.tlapl.us/</link>
        <url>https://docs.tlapl.us/_media/logo.png</url>
    </image>
    <item rdf:about="https://docs.tlapl.us/using:vscode:automatic_module_parsing?rev=1762248279&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-04T09:24:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>automatic_module_parsing</title>
        <link>https://docs.tlapl.us/using:vscode:automatic_module_parsing?rev=1762248279&amp;do=diff</link>
        <description>Automatic Module Parsing

The extension provides the TLA+: Parse module command for both translating a PlusCal algorithm to TLA+ code and parsing the resulting TLA+ module. This command is so important in the specification writing process that you might want it to be executed every time you save a .tla file to get quicker response.</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:boxed_comments?rev=1729369410&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T20:23:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>boxed_comments</title>
        <link>https://docs.tlapl.us/using:vscode:boxed_comments?rev=1729369410&amp;do=diff</link>
        <description>Boxed Comments

It’s a common practice to use boxed comments in TLA+ specifications:


(**************************************************************)
(* This is a boxed comment.                                   *)
(* Such comment format is used in lots of specifications.     *)
(**************************************************************)</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:caveats?rev=1729364150&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T18:55:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>caveats</title>
        <link>https://docs.tlapl.us/using:vscode:caveats?rev=1729364150&amp;do=diff</link>
        <description>Caveats

Here you can find a list of known minor problems that you might encounter while working with the extension. We hope they’ll be fixed some day, but at the moment, just be aware of them.

PlusCal algorithm boundaries detection

The following PlusCal algorithm declarations are totally correct:</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:commands?rev=1729364164&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T18:56:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>commands</title>
        <link>https://docs.tlapl.us/using:vscode:commands?rev=1729364164&amp;do=diff</link>
        <description>Commands

The extension provides the following commands in the Command Palette:

	*  TLA+: Parse module for translating PlusCal to TLA+ and checking syntax of the resulting specification.
	*  TLA+: Check model for running the TLC model checker on the TLA+ specification.</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:fonts?rev=1729365689&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T19:21:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fonts</title>
        <link>https://docs.tlapl.us/using:vscode:fonts?rev=1729365689&amp;do=diff</link>
        <description>Fonts

TLA+ widely uses the language of mathematics, and its syntax contains great deal of character sequences that represent mathematical symbols. So why not use those symbols directly when displaying specifications in the text editor?

There’re two levels of visualization improvements:</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:formatting_preferences?rev=1729364593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T19:03:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>formatting_preferences</title>
        <link>https://docs.tlapl.us/using:vscode:formatting_preferences?rev=1729364593&amp;do=diff</link>
        <description>Formatting Preferences

By default, the extension is configured to help you with formatting the code while you’re typing. If you want to change any aspect of this behavior, you can do it by editing the tlaplus language settings. To do that:

	*  Open the</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:getting_started?rev=1758132021&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-09-17T18:00:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>getting_started</title>
        <link>https://docs.tlapl.us/using:vscode:getting_started?rev=1758132021&amp;do=diff</link>
        <description>Getting Started

The easiest way to get a simple working model is to create an empty PlusCal algorithm, translate it into a TLA+ specification and run the TLC tool on it. Here’s a step by step instruction:

Create a specification file. Let’s name it</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:installing_java?rev=1729875489&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-25T16:58:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>installing_java</title>
        <link>https://docs.tlapl.us/using:vscode:installing_java?rev=1729875489&amp;do=diff</link>
        <description>Installing Java

Why Java?

The extension uses the official TLA&lt;sup&gt;+&lt;/sup&gt; tools to support such features as PlusCal-to-TLA+ translation, module parsing, model checking etc. These tools need JVM (Java Virtual Machine) to run, and the extension doesn’t come with a JVM onboard. Thus, it requires a JVM to be installed on the user’s computer.</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:java_options?rev=1729365781&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T19:23:01+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>java_options</title>
        <link>https://docs.tlapl.us/using:vscode:java_options?rev=1729365781&amp;do=diff</link>
        <description>Java Options

The Java: Options setting allows you to provide additional options that will be passed to the Java process when running TLA+ tools.

At the same time, the extension itself adds a couple of default options when running Java. Thus, it sometimes has to “merge” those default options with ones provided by the user. During this merging, the user settings always take precedence.</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:keyboard_shortcuts?rev=1729369471&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T20:24:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>keyboard_shortcuts</title>
        <link>https://docs.tlapl.us/using:vscode:keyboard_shortcuts?rev=1729369471&amp;do=diff</link>
        <description>Keyboard Shortcuts

The extension provides various commands, at least some of which you’ll probably want to use often enough to have keyboard shortcuts for them. The extension purposefully doesn’t provide predefined shortcuts to not meddle with the existing user settings.</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:migrating_from_tlatoolbox?rev=1760128798&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-10T20:39:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>migrating_from_tlatoolbox</title>
        <link>https://docs.tlapl.us/using:vscode:migrating_from_tlatoolbox?rev=1760128798&amp;do=diff</link>
        <description>Migrating from TLA+ Toolbox

TLA+ Toolbox is an IDE based on Eclipse, and for a long time it has been the official environment to work with TLA+ tools. See: &lt;https://lamport.azurewebsites.net/tla/toolbox.html&gt;

Since around 2020 the development focus has moved to improve the VScode plugin experience. The TLA+ Toolbox has now moved to archived mode. The current bugs won&#039;t be fixed and as as dependency rots, eventually it will stop being distributed as well. Therefore it is not recommended for dai…</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:settings?rev=1762248560&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-04T09:29:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>settings</title>
        <link>https://docs.tlapl.us/using:vscode:settings?rev=1762248560&amp;do=diff</link>
        <description>Settings

This section provides the list of various settings that allow you to configure the extension to fit your preferences.

Extension Settings

These settings are available in the Extensions → TLA+ section of the Settings panel:

	*  Java: Home allows to provide location of the JVM that the extension must use for running TLA</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:start?rev=1748731302&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-31T22:41:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://docs.tlapl.us/using:vscode:start?rev=1748731302&amp;do=diff</link>
        <description>Visual Studio Code Extension

This is the fastest and easiest way to get started with TLA+ and TLC.

	*  Download and install Visual Studio Code
	*  Open it, go to the Marketplace panel, find the &quot;TLA+&quot; extension and click &quot;Install&quot;. Make sure to install TLA+ from TLA+ Foundation. Url:</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:troubleshooting?rev=1729364389&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T18:59:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>troubleshooting</title>
        <link>https://docs.tlapl.us/using:vscode:troubleshooting?rev=1729364389&amp;do=diff</link>
        <description>Troubleshooting

Here is the list of troubles the user may encounter and recipes for dealing with them.

Message: Unsupported Java version: X

The extension shows this message when it finds out that the version of the JVM you use for running the TLA+</description>
    </item>
    <item rdf:about="https://docs.tlapl.us/using:vscode:visualizing_states?rev=1729369348&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-19T20:22:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>visualizing_states</title>
        <link>https://docs.tlapl.us/using:vscode:visualizing_states?rev=1729369348&amp;do=diff</link>
        <description>Visualizing States

TLC model checker can dump generated states to a file in DOT notation. Such .dot files can be visualized as graphs right in VS Code with the help of additional extensions. Here’re the most popular of them:
 - Graphviz Interactive Preview,
 - Graphviz Preview,
 - Graphviz (dot) language support for Visual Studio Code.

To generate .dot files while running model checking, add</description>
    </item>
</rdf:RDF>
