This extension provides spec macro script (
During migration of my PCs, I deleted my Visual Studio Marketplace publisher account by mistake.
I recreated a new account with the same name (
cited from CSS - Certified Scientific Software homepage.
This extension supports the following features:
These features cover both user-defined symbols and built-in symbols. Built-in symbols and always global. User-defined symbols declared at the top level (i.e., not in a code block, curly brackets) are global; they are scanned from open documents and optionally in files in the workspace. User-defined symbols in code blocks are local; they are listed only when they are accessible from the current cursor position.
The help text of built-in symbols can also be shown as an indepedent document; select spec: Open Reference Manual from Command Palette (Ctrl+Shit+P).
This extension was developed with reference to the recent official PDF document about spec release 6 (version 3 of the spec documentation, printed 16 July 2017). The help text of built-in symbols are cited from this document.
The extension assumes UTF-8 as the file encoding in workspace scan, regardless of user settings or selection in current editor. This does not mean the developer garantees UTF-8 characters are safe for spec interpreters.
The spec grammar is torelant, lazy in other word. It is difficult to perfectly mimic its behavior. Instead, this extension requires stricter coding than the spec interpreters does. For example, spec interpreters evaluate the following two lines equivalently:
but this extension shows an alert or error on the first line ("/" is the division operator and "." is not for any literal, symbols or operators.) because it expects explicit quotation marks for a string literal.
This extention contributes the follwing settings:
One can find the settings in Extension / spec in the Settings window. Read Visual Studio Code User and Workspace Settings if one has difficulty in setting them.
This extension is still beta and the identifiers (dot-separated string) of these settings may be changed in future releases.
Also read GitHub issues.