From e6a6e72e3ce7e612e6f397bcab9de6439210152b Mon Sep 17 00:00:00 2001 From: Florian Knoch Date: Sat, 8 Feb 2020 17:27:36 +0100 Subject: [PATCH] Initial Commit --- .vscode/launch.json | 16 ++++++ CHANGELOG.md | 9 ++++ README.md | 65 +++++++++++++++++++++++ language-configuration.json | 30 +++++++++++ package.json | 14 +++++ syntaxes/markdown-onPoint.tmLanguage.json | 23 ++++++++ vsc-extension-quickstart.md | 34 ++++++++++++ 7 files changed, 191 insertions(+) create mode 100644 .vscode/launch.json create mode 100755 CHANGELOG.md create mode 100755 README.md create mode 100755 language-configuration.json create mode 100755 package.json create mode 100755 syntaxes/markdown-onPoint.tmLanguage.json create mode 100755 vsc-extension-quickstart.md diff --git a/.vscode/launch.json b/.vscode/launch.json new file mode 100644 index 0000000..3c90697 --- /dev/null +++ b/.vscode/launch.json @@ -0,0 +1,16 @@ +// A launch configuration that launches the extension inside a new window +// Use IntelliSense to learn about possible attributes. +// Hover to view descriptions of existing attributes. +// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 +{ + "version": "0.2.0", + "configurations": [{ + "name": "Extension", + "type": "extensionHost", + "request": "launch", + "runtimeExecutable": "${execPath}", + "args": [ + "--extensionDevelopmentPath=${workspaceFolder}" + ] + }] +} \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100755 index 0000000..3f6776d --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,9 @@ +# Change Log + +All notable changes to the "markdown-onpoint" extension will be documented in this file. + +Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file. + +## [Unreleased] + +- Initial release \ No newline at end of file diff --git a/README.md b/README.md new file mode 100755 index 0000000..d23f6ee --- /dev/null +++ b/README.md @@ -0,0 +1,65 @@ +# markdown-onpoint README + +This is the README for your extension "markdown-onpoint". After writing up a brief description, we recommend including the following sections. + +## Features + +Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file. + +For example if there is an image subfolder under your extension project workspace: + +\!\[feature X\]\(images/feature-x.png\) + +> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow. + +## Requirements + +If you have any requirements or dependencies, add a section describing those and how to install and configure them. + +## Extension Settings + +Include if your extension adds any VS Code settings through the `contributes.configuration` extension point. + +For example: + +This extension contributes the following settings: + +* `myExtension.enable`: enable/disable this extension +* `myExtension.thing`: set to `blah` to do something + +## Known Issues + +Calling out known issues can help limit users opening duplicate issues against your extension. + +## Release Notes + +Users appreciate release notes as you update your extension. + +### 1.0.0 + +Initial release of ... + +### 1.0.1 + +Fixed issue #. + +### 1.1.0 + +Added features X, Y, and Z. + +----------------------------------------------------------------------------------------------------------- + +## Working with Markdown + +**Note:** You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts: + +* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux) +* Toggle preview (`Shift+CMD+V` on macOS or `Shift+Ctrl+V` on Windows and Linux) +* Press `Ctrl+Space` (Windows, Linux) or `Cmd+Space` (macOS) to see a list of Markdown snippets + +### For more information + +* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown) +* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/) + +**Enjoy!** diff --git a/language-configuration.json b/language-configuration.json new file mode 100755 index 0000000..aa25710 --- /dev/null +++ b/language-configuration.json @@ -0,0 +1,30 @@ +{ + "comments": { + // symbol used for single line comment. Remove this entry if your language does not support line comments + "lineComment": "//", + // symbols used for start and end a block comment. Remove this entry if your language does not support block comments + "blockComment": [ "/*", "*/" ] + }, + // symbols used as brackets + "brackets": [ + ["{", "}"], + ["[", "]"], + ["(", ")"] + ], + // symbols that are auto closed when typing + "autoClosingPairs": [ + ["{", "}"], + ["[", "]"], + ["(", ")"], + ["\"", "\""], + ["'", "'"] + ], + // symbols that that can be used to surround a selection + "surroundingPairs": [ + ["{", "}"], + ["[", "]"], + ["(", ")"], + ["\"", "\""], + ["'", "'"] + ] +} \ No newline at end of file diff --git a/package.json b/package.json new file mode 100755 index 0000000..72f1792 --- /dev/null +++ b/package.json @@ -0,0 +1,14 @@ +{ + "name": "markdown-onPoint", + "version": "0.0.1", + "engines": { + "vscode": "^1.22.0" + }, + "contributes": { + "grammars": [{ + "path": "./syntaxes/markdown-onPoint.tmLanguage.json", + "scopeName": "markdown-onPoint.injection", + "injectTo": ["text.html.markdown"] + }] + } +} \ No newline at end of file diff --git a/syntaxes/markdown-onPoint.tmLanguage.json b/syntaxes/markdown-onPoint.tmLanguage.json new file mode 100755 index 0000000..13a68aa --- /dev/null +++ b/syntaxes/markdown-onPoint.tmLanguage.json @@ -0,0 +1,23 @@ +{ + "scopeName": "markdown-onPoint.injection", + "injectionSelector": "L:meta.paragraph.markdown", + "patterns": [ + { "include": "#slide-annotation" }, + { "include": "#annotation" }, + { "include": "#fragment" } + ], + "repository": { + "slide-annotation": { + "match": "@slide(\\(.+\\))?", + "name": "markup.heading.slide-annotation" + }, + "annotation": { + "match": "@.+(\\(.+\\))?", + "name": "comment.annotation" + }, + "fragment": { + "match": "\\+\\?", + "name": "comment.fragment" + } + } +} \ No newline at end of file diff --git a/vsc-extension-quickstart.md b/vsc-extension-quickstart.md new file mode 100755 index 0000000..0c09086 --- /dev/null +++ b/vsc-extension-quickstart.md @@ -0,0 +1,34 @@ +# Welcome to your VS Code Extension + +## How to run the extension + +* getting started: https://code.visualstudio.com/api/get-started/your-first-extension +* syntax highlighting extension sample: https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide + +## What's in the folder + +* This folder contains all of the files necessary for your extension. +* `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. +* `syntaxes/markdown-onPoint.tmLanguage.json` - this is the Text mate grammar file that is used for tokenization. +* `language-configuration.json` - this is the language configuration, defining the tokens that are used for comments and brackets. + +## Get up and running straight away + +* Make sure the language configuration settings in `language-configuration.json` are accurate. +* Press `F5` to open a new window with your extension loaded. +* Create a new file with a file name suffix matching your language. +* Verify that syntax highlighting works and that the language configuration settings are working. + +## Make changes + +* You can relaunch the extension from the debug toolbar after making changes to the files listed above. +* You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes. + +## Add more language features + +* To add features such as intellisense, hovers and validators check out the VS Code extenders documentation at https://code.visualstudio.com/docs + +## Install your extension + +* To start using your extension with Visual Studio Code copy it into the `/.vscode/extensions` folder and restart Code. +* To share your extension with the world, read on https://code.visualstudio.com/docs about publishing an extension.