···11+// A launch configuration that launches the extension inside a new window
22+// Use IntelliSense to learn about possible attributes.
33+// Hover to view descriptions of existing attributes.
44+// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
55+{
66+ "version": "0.2.0",
77+ "configurations": [
88+ {
99+ "name": "Extension",
1010+ "type": "extensionHost",
1111+ "request": "launch",
1212+ "args": [
1313+ "--extensionDevelopmentPath=${workspaceFolder}"
1414+ ]
1515+ }
1616+ ]
1717+}
···11+# Change Log
22+33+All notable changes to the "issurge" extension will be documented in this file.
44+55+Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
66+77+## [Unreleased]
88+99+- Initial release
+3
vscode-extension/README.md
···11+# issurge's vscode extension
22+33+This extension provides syntax highlighting support for issurge files
+6
vscode-extension/language-configuration.json
···11+{
22+ "comments": {
33+ // symbol used for single line comment. Remove this entry if your language does not support line comments
44+ "lineComment": "//"
55+ }
66+}
···11+# Welcome to your VS Code Extension
22+33+## What's in the folder
44+55+* This folder contains all of the files necessary for your extension.
66+* `package.json` - this is the manifest file in which you declare your language support and define the location of the grammar file that has been copied into your extension.
77+* `syntaxes/issurge.tmLanguage.json` - this is the Text mate grammar file that is used for tokenization.
88+* `language-configuration.json` - this is the language configuration, defining the tokens that are used for comments and brackets.
99+1010+## Get up and running straight away
1111+1212+* Make sure the language configuration settings in `language-configuration.json` are accurate.
1313+* Press `F5` to open a new window with your extension loaded.
1414+* Create a new file with a file name suffix matching your language.
1515+* Verify that syntax highlighting works and that the language configuration settings are working.
1616+1717+## Make changes
1818+1919+* You can relaunch the extension from the debug toolbar after making changes to the files listed above.
2020+* You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.
2121+2222+## Add more language features
2323+2424+* To add features such as IntelliSense, hovers and validators check out the VS Code extenders documentation at https://code.visualstudio.com/docs
2525+2626+## Install your extension
2727+2828+* To start using your extension with Visual Studio Code copy it into the `<user home>/.vscode/extensions` folder and restart Code.
2929+* To share your extension with the world, read on https://code.visualstudio.com/docs about publishing an extension.