Update relative links
This commit is contained in:
Greg Van Liew
Родитель
f95a79b1f3
Коммит
7811901ee9
|
|
@ -138,7 +138,7 @@ The VS Code portal is able to show the correct key bindings depending on the rea
|
|||
|
||||
To enable this for keyboard shortcuts, use the format `kb(workbench.action.files.openFile)` where the command name is included in parentheses.
|
||||
|
||||
>For a list of key bindings and the relevant `Command Ids` review the [key bindings document](https://code.visualstudio.com/docs/editor/keybindings).
|
||||
>For a list of key bindings and the relevant `Command Ids` review the [key bindings document](https://code.visualstudio.com/docs/getstarted/keybindings).
|
||||
|
||||
If you are listing out multiple key bindings, you can use a table.
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ And at the same time, we open-sourced the VS Code [repository](https://github.co
|
|||
|
||||
Today, Visual Studio Code delivers on many of the aspects that we imagined during incubation. VS Code has great editing and navigation [experiences](/docs/editor/editingevolved), streamlined [debugging](/docs/editor/debugging), and built-in [Git support](/docs/editor/versioncontrol).
|
||||
|
||||
Developers today love VS Code for its powerful set of built-in features, intuitive editing and debugging experiences, performance and responsiveness, and great language and platform support. The VS Code download is under 40MB including support for 9 additional [languages](/docs/customization/locales) (Simplified Chinese, Traditional Chinese, French, German, Italian, Japanese, Korean, Russian and Spanish) and it installs in seconds. With the help of developers like [@zersiax](https://twitter.com/zersiax), VS Code is now [accessible](/docs/editor/accessibility) to visually impaired developers on Windows and soon on OS X and Linux.
|
||||
Developers today love VS Code for its powerful set of built-in features, intuitive editing and debugging experiences, performance and responsiveness, and great language and platform support. The VS Code download is under 40MB including support for 9 additional [languages](/docs/getstarted/locales) (Simplified Chinese, Traditional Chinese, French, German, Italian, Japanese, Korean, Russian and Spanish) and it installs in seconds. With the help of developers like [@zersiax](https://twitter.com/zersiax), VS Code is now [accessible](/docs/editor/accessibility) to visually impaired developers on Windows and soon on OS X and Linux.
|
||||
|
||||
## Community at its Core
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ To help new users, today we are announcing a set of introductory videos. These v
|
|||
|
||||
## Take a Look
|
||||
|
||||
Navigate to [Intro Videos - Overview](/docs/introvideos/overview.md) to get started.
|
||||
Navigate to [Intro Videos - Overview](/docs/getstarted/introvideos.md) to get started.
|
||||
|
||||
Below is the first video covering downloading, installing, and the basics of using VS Code:
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ Most of the team now runs on the Seti icons so we decided to include them in the
|
|||
|
||||
## Create your own Icon Theme
|
||||
|
||||
It is incredibly easy for extension authors to create your own File Icon Theme packs, check out the raw documentation [here](https://github.com/Microsoft/vscode/issues/10804) and the ["Adding a new Icon Theme"](/docs/customization/themes.md#adding-a-new-icon-theme) topic in the VS Code docs. Looking ahead, we will continue to fill out the API based on your feedback.
|
||||
It is incredibly easy for extension authors to create your own File Icon Theme packs, check out the raw documentation [here](https://github.com/Microsoft/vscode/issues/10804) and the ["Adding a new Icon Theme"](/docs/extensions/themes-snippets-colorizers.md#adding-a-new-icon-theme) topic in the VS Code docs. Looking ahead, we will continue to fill out the API based on your feedback.
|
||||
|
||||
Thanks again for all of your feedback and thanks to Roberto for building a popular extension and helping us deliver great APIs.
|
||||
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ These extensions are in preview because we want your feedback. There are still m
|
|||
}
|
||||
```
|
||||
|
||||
Do you have other editors or IDEs you'd like to make a keymap for? Simply follow the instructions in the [`contributes.keybindings` section](/docs/extensionAPI/extension-points#_contributeskeybindings) and the [Customization -> Keybindings document](/docs/customization/keybindings).
|
||||
Do you have other editors or IDEs you'd like to make a keymap for? Simply follow the instructions in the [`contributes.keybindings` section](/docs/extensionAPI/extension-points#_contributeskeybindings) and the [Keybindings document](/docs/getstarted/keybindings).
|
||||
|
||||
## It's raining keyboard shortcuts
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Some of my favorite themes are:
|
|||
|
||||
Want to create your own theme? See the [documentation](https://code.visualstudio.com/docs/extensionAPI/extension-points#_contributesthemes) to get started.
|
||||
|
||||
VS Code also supports [File Icon](https://code.visualstudio.com/docs/customization/themes#_select-an-icon-theme) themes to add images to files and folders in the UI. You can preview your installed File Icon themes in VS Code by **File** > **Preferences** > **File Icon Theme** or by opening the **Command Palette** and typing "file icon".
|
||||
VS Code also supports [File Icon](https://code.visualstudio.com/docs/getstarted/themes#_select-an-icon-theme) themes to add images to files and folders in the UI. You can preview your installed File Icon themes in VS Code by **File** > **Preferences** > **File Icon Theme** or by opening the **Command Palette** and typing "file icon".
|
||||
|
||||
Here are two File Icon themes I really like:
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ You can increase the Zoom level in VS Code with the **View** > **Zoom In** comma
|
|||
|
||||
## Persisted Zoom Level
|
||||
|
||||
When you adjust the zoom level with the **View** > **Zoom In / Out** commands, the zoom level is persisted in the `window.zoomLevel` [setting](/docs/customization/userandworkspace.md). The default value is 0 and each increment increases the zoom level by 20%.
|
||||
When you adjust the zoom level with the **View** > **Zoom In / Out** commands, the zoom level is persisted in the `window.zoomLevel` [setting](/docs/getstarted/settings.md). The default value is 0 and each increment increases the zoom level by 20%.
|
||||
|
||||
## High Contrast Theme
|
||||
|
||||
|
|
@ -36,7 +36,7 @@ VS Code also has many preset keyboard shortcuts for commands. These are displaye
|
|||
|
||||
|
||||
|
||||
You can also set your own keyboard shortcuts. **File** > **Preferences** > **Keyboard Shortcuts** brings up the **Default Keyboard Shortcuts** in the left pane and your customizable `keybindings.json` on the right. See [Key Bindings](/docs/customization/keybindings.md) for more details on customizing or adding your own keyboard shortcuts.
|
||||
You can also set your own keyboard shortcuts. **File** > **Preferences** > **Keyboard Shortcuts** brings up the **Default Keyboard Shortcuts** in the left pane and your customizable `keybindings.json` on the right. See [Key Bindings](/docs/getstarted/keybindings.md) for more details on customizing or adding your own keyboard shortcuts.
|
||||
|
||||
## Tab Navigation
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Key|Command|Command id
|
|||
`kb(cursorColumnSelectPageDown)`|Column Select Page Down|`cursorColumnSelectPageDown`
|
||||
`kb(cursorColumnSelectPageUp)`|Column Select Page Up|`cursorColumnSelectPageUp`
|
||||
|
||||
You can [edit](/docs/customization/keybindings.md) your `keybindings.json` to bind them to something more familiar if you wish.
|
||||
You can [edit](/docs/getstarted/keybindings.md) your `keybindings.json` to bind them to something more familiar if you wish.
|
||||
|
||||
## Save / Auto Save
|
||||
|
||||
|
|
@ -110,13 +110,13 @@ When you type text into the Replace text box, you will see a diff display of the
|
|||
|
||||
## IntelliSense
|
||||
|
||||
We'll always offer word completion, but for the rich [languages](/docs/languages/overview.md), such as JavaScript, JSON, HTML, CSS, Less, Sass, C# and TypeScript, we offer a true IntelliSense experience. If a language service knows possible completions, the IntelliSense suggestions will pop up as you type. You can always manually trigger it with `kb(editor.action.triggerSuggest)`. By default, `kbstyle(Tab)` or `kbstyle(Enter)` are the accept keyboard triggers but you can also [customize these key bindings](/docs/customization/keybindings.md).
|
||||
We'll always offer word completion, but for the rich [languages](/docs/languages/overview.md), such as JavaScript, JSON, HTML, CSS, Less, Sass, C# and TypeScript, we offer a true IntelliSense experience. If a language service knows possible completions, the IntelliSense suggestions will pop up as you type. You can always manually trigger it with `kb(editor.action.triggerSuggest)`. By default, `kbstyle(Tab)` or `kbstyle(Enter)` are the accept keyboard triggers but you can also [customize these key bindings](/docs/getstarted/keybindings.md).
|
||||
|
||||
> **Tip:** The suggestions filtering supports CamelCase so you can type the letters which are upper cased in a method name to limit the suggestions. For example, "cra" will quickly bring up "createApplication".
|
||||
|
||||
> **Tip:** IntelliSense suggestions can be configured via the `editor.quickSuggestions` and `editor.suggestOnTriggerCharacters` [settings](/docs/customization/userandworkspace.md).
|
||||
> **Tip:** IntelliSense suggestions can be configured via the `editor.quickSuggestions` and `editor.suggestOnTriggerCharacters` [settings](/docs/getstarted/settings.md).
|
||||
|
||||
JavaScript and TypeScript developers can take advantage of the [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) type definition (typings) file repository to get IntelliSense for common JavaScript libraries (Node.js, React, Angular). You can find a good explanation on using `typings` files in the [JavaScript language](/docs/languages/javascript#_intellisense) topic and the [Node.js](/docs/runtimes/nodejs#_intellisense-and-typings) walkthrough.
|
||||
JavaScript and TypeScript developers can take advantage of the [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) type definition (typings) file repository to get IntelliSense for common JavaScript libraries (Node.js, React, Angular). You can find a good explanation on using `typings` files in the [JavaScript language](/docs/languages/javascript#_intellisense) topic and the [Node.js](/docs/nodejs/nodejs-tutorial.md#_intellisense-and-typings) tutorial.
|
||||
|
||||
Learn more in the [IntelliSense document](/docs/editor/intellisense.md).
|
||||
|
||||
|
|
@ -157,12 +157,11 @@ Then choose an encoding.
|
|||
You've covered the basic user interface - there is a lot more to VS Code. Read on to find out about:
|
||||
|
||||
* [Intro Video - Setup and Basics](/docs/introvideos/basics.md) - Watch a tutorial on the basics of VS Code.
|
||||
* [User/Workspace Settings](/docs/customization/userandworkspace.md) - Learn how to configure VS Code to your preferences through user and workspace settings.
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - Lint, IntelliSense, Lightbulbs, Peek and Goto Definition, and more
|
||||
* [User/Workspace Settings](/docs/getstarted/settings.md) - Learn how to configure VS Code to your preferences through user and workspace settings.
|
||||
* [Code Navigation](/docs/editor/editingevolved.md) - Peek and Goto Definition, and more
|
||||
* [Integrated Terminal](/docs/editor/integrated-terminal.md) - Learn about the integrated terminal for quickly performing command line tasks from within VS Code.
|
||||
* [IntelliSense](/docs/editor/intellisense.md) - VS Code brings smart code completions.
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines
|
||||
* [Customization](/docs/customization/overview.md) - Themes, settings, and keyboard bindings
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
@ -174,7 +173,7 @@ You've covered the basic user interface - there is a lot more to VS Code. Read
|
|||
|
||||
**Q: How do I turn on word wrap?**
|
||||
|
||||
**A:** You can control word wrap through the `editor.wrappingColumn` [setting](/docs/customization/userandworkspace.md). By default `editor.wrappingColumn` is set to 300 characters. You can adjust the column width or set the value to zero to wrap on the editor viewport width:
|
||||
**A:** You can control word wrap through the `editor.wrappingColumn` [setting](/docs/getstarted/settings.md). By default `editor.wrappingColumn` is set to 300 characters. You can adjust the column width or set the value to zero to wrap on the editor viewport width:
|
||||
|
||||
```json
|
||||
"editor.wrappingColumn": 0
|
||||
|
|
@ -186,4 +185,4 @@ You can also add vertical column rulers to the editor with the `editor.rulers` s
|
|||
|
||||
**Q: How can I show more files in the OPEN EDITORS section?**
|
||||
|
||||
**A:** You can configure the appearance of **OPEN EDITORS** through your [settings](/docs/customization/userandworkspace.md). For example, you can set the maximum number of visible files before a scroll bar appears via the `explorer.openEditors.visible` setting and whether the **OPEN EDITORS** section should dynamically set its height via `explorer.openEditors.dynamicHeight`.
|
||||
**A:** You can configure the appearance of **OPEN EDITORS** through your [settings](/docs/getstarted/settings.md). For example, you can set the maximum number of visible files before a scroll bar appears via the `explorer.openEditors.visible` setting and whether the **OPEN EDITORS** section should dynamically set its height via `explorer.openEditors.dynamicHeight`.
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Below are several popular extension which include debugging support:
|
|||
|
||||
The following documentation is based on the built-in [Node.js](https://nodejs.org/) debugger, but most of the concepts and features are applicable to other debuggers as well.
|
||||
|
||||
It is helpful to first create a sample Node.js application before reading about debugging. You can follow the [Node.js walkthrough](/docs/runtimes/nodejs.md) to install Node.js and create a simple "Hello World" JavaScript application (`app.js`). Once you have a simple application all set up, this page will take you through VS Code debugging features.
|
||||
It is helpful to first create a sample Node.js application before reading about debugging. You can follow the [Node.js tutorial](/docs/nodejs/nodejs-tutorial.md) to install Node.js and create a simple "Hello World" JavaScript application (`app.js`). Once you have a simple application all set up, this page will take you through VS Code debugging features.
|
||||
|
||||
## Debug View
|
||||
|
||||
|
|
@ -252,7 +252,7 @@ Expressions can be evaluated in the **Debug Console**. To open the Debug Console
|
|||
|
||||
To learn about VS Code's Node.js debugging support, take a look at:
|
||||
|
||||
* [Node.js](/docs/editor/node-debugging.md) - Node.js debugging is included in VS Code.
|
||||
* [Node.js](/docs/nodejs/nodejs-debugging.md) - Node.js debugging is included in VS Code.
|
||||
|
||||
To see a tutorial on the basics of Node.js debugging, check out:
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ We think there's nothing worse than a big context switch when all you want is to
|
|||
|
||||
You can navigate between different references in the peeked editor and make quick edits right there. Clicking on the peeked editor filename or double-clicking in the result list will open the reference in the outer editor.
|
||||
|
||||
> **Tip:** Additionally, the peek window is closed if you press `kbstyle(Escape)` or double-click in the peek editor region. You can disable this behavior with the `editor.stablePeek` [setting](/docs/customization/userandworkspace.md).
|
||||
> **Tip:** Additionally, the peek window is closed if you press `kbstyle(Escape)` or double-click in the peek editor region. You can disable this behavior with the `editor.stablePeek` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
## Bracket matching
|
||||
|
||||
|
|
@ -107,7 +107,6 @@ Now that you know how the editor works, time to try a few other things...
|
|||
|
||||
* [Intro Video - Code Editing](/docs/introvideos/codeediting.md) - Watch an introductory video on code editing features.
|
||||
* [The Basics](/docs/editor/codebasics.md) - In case you missed a basic orientation around VS Code.
|
||||
* [Customization](/docs/customization/overview.md) - Configure VS Code the way you want - Themes, Settings, Display Language
|
||||
* [Key Bindings](/docs/customization/keybindings.md) - Learn how to modify key bindings to your preference.
|
||||
* [Key Bindings](/docs/getstarted/keybindings.md) - Learn how to modify key bindings to your preference.
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines.
|
||||
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ You can quickly look for extension updates by using the **Show Outdated Extensio
|
|||
|
||||
## Auto Update Extensions
|
||||
|
||||
If you would like your installed extensions to be updated automatically, you can use the `extensions.autoUpdate` [setting](/docs/customization/userandworkspace.md). When set to `true`, VS Code will download new versions of outdated extensions automatically and you will just need to restart VS Code when you see the blue **Enable** button in the Installed Extensions list.
|
||||
If you would like your installed extensions to be updated automatically, you can use the `extensions.autoUpdate` [setting](/docs/getstarted/settings.md). When set to `true`, VS Code will download new versions of outdated extensions automatically and you will just need to restart VS Code when you see the blue **Enable** button in the Installed Extensions list.
|
||||
|
||||
## Disable an Extension
|
||||
|
||||
|
|
@ -133,7 +133,6 @@ VS Code prompts a user to install the recommended extensions when a workspace is
|
|||
Here are a few topics you may find interesting...
|
||||
|
||||
* [Publishing to the Marketplace](/docs/tools/vscecli.md) - Publish your own customization or extension to the VS Code Marketplace
|
||||
* [Customization](/docs/customization/overview.md) - Learn how to integrate TextMate themes, colorizers and snippets into Visual Studio Code.
|
||||
* [Yo Code](/docs/tools/yocode.md) - Learn how the Yo Code extension generator can scaffold out new extensions and package existing TextMate files.
|
||||
* [Extending Visual Studio Code](/docs/extensions/overview.md) - Start learning about VS Code extensibility
|
||||
* [Your First Extension](/docs/extensions/example-hello-world.md) - Try creating a simple Hello World extension
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Remove terminal instances by pressing the trash can button.
|
|||
|
||||
## Configuration
|
||||
|
||||
The shell used defaults to `$SHELL` on Linux and OS X, and `%COMSPEC%` on Windows. These can be overridden manually by setting `terminal.integrated.shell.*` in [settings](/docs/customization/userandworkspace.md). Arguments can be passed to the terminal shell on Linux and OS X using the `terminal.integrated.shellArgs.*` settings.
|
||||
The shell used defaults to `$SHELL` on Linux and OS X, and `%COMSPEC%` on Windows. These can be overridden manually by setting `terminal.integrated.shell.*` in [settings](/docs/getstarted/settings.md). Arguments can be passed to the terminal shell on Linux and OS X using the `terminal.integrated.shellArgs.*` settings.
|
||||
|
||||
### Windows
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ You can customize your IntelliSense experience in settings and key bindings.
|
|||
|
||||
### Settings
|
||||
|
||||
The settings shown below are the default settings. You can change these settings in your `settings.json` file as described in [User and Workspace Settings](/docs/customization/userandworkspace.md).
|
||||
The settings shown below are the default settings. You can change these settings in your `settings.json` file as described in [User and Workspace Settings](/docs/getstarted/settings.md).
|
||||
|
||||
```javascript
|
||||
{
|
||||
|
|
@ -101,7 +101,7 @@ By default, VS Code shows snippets and completion proposals in one widget. You c
|
|||
|
||||
### Key Bindings
|
||||
|
||||
The key binding shown below is the default key binding. You can change this key binding in your `keybindings.json` file as described in [Key Bindings](/docs/customization/keybindings.md).
|
||||
The key binding shown below is the default key binding. You can change this key binding in your `keybindings.json` file as described in [Key Bindings](/docs/getstarted/keybindings.md).
|
||||
|
||||
> **Note:** There are many more key bindings relating to IntelliSense. Simply open the **Default Keyboard Shortcuts** (**File** > **Preferences** > **Keyboard Shortcuts**) and search for "suggest".
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ A particular language extension may not support all the VS Code IntelliSense fea
|
|||
IntelliSense is just one of VS Code's powerful features. Read on to learn more:
|
||||
|
||||
* [JavaScript](/docs/languages/javascript.md) - Get the most out of your JavaScript development, including configuring IntelliSense.
|
||||
* [Node.js](/docs/runtimes/nodejs.md#intellisense-and-typings) - See an example of IntelliSense in action in the Node.js walkthrough.
|
||||
* [Node.js](/docs/nodejs/nodejs-tutorial.md#intellisense-and-typings) - See an example of IntelliSense in action in the Node.js walkthrough.
|
||||
* [Debugging](/docs/editor/debugging.md) - Learn how to set up debugging for your application.
|
||||
|
||||
## Common Questions
|
||||
|
|
|
|||
|
|
@ -105,10 +105,9 @@ text ::= .*
|
|||
|
||||
TBD
|
||||
|
||||
* [Colorizers and Bracket Matchers](/docs/customization/colorizer.md) - Learn how to import TextMate colorizers
|
||||
* [Custom themes](/docs/customization/themes.md) - Learn how to import existing TextMate themes.
|
||||
* [Custom themes](/docs/extensions/themes-snippets-colorizers.md) - Learn how to import existing TextMate themes.
|
||||
* [Extending Visual Studio Code](/docs/extensions/overview.md) - Learn about other ways to extend VS Code
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - Learn more about the VS Code editor's capabilities
|
||||
* [Code Navigation](/docs/editor/editingevolved.md) - Learn more about the VS Code editor's capabilities
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ The `git branch` command lets you quickly create a new branch. Just provide the
|
|||
|
||||
Given that your repository is connected to some remote and that your checked out branch has an [upstream link](http://git-scm.com/book/ch3-5.html) to a branch in that remote, VS Code offers you useful actions to **push**, **pull** and **sync** that branch (the latter will run a **pull** command followed by a **push** command). You can find these actions in the `...` menu.
|
||||
|
||||
>**Tip:** You should [set up a credential helper](https://help.github.com/articles/caching-your-github-password-in-git/) to avoid getting asked for credentials every time VS Code talks to your Git remotes. If you don't do this, you may want to consider disabling automatic fetching via the `git.autofetch` [setting](/docs/customization/userandworkspace.md) to reduce the number of prompts you get.
|
||||
>**Tip:** You should [set up a credential helper](https://help.github.com/articles/caching-your-github-password-in-git/) to avoid getting asked for credentials every time VS Code talks to your Git remotes. If you don't do this, you may want to consider disabling automatic fetching via the `git.autofetch` [setting](/docs/getstarted/settings.md) to reduce the number of prompts you get.
|
||||
|
||||
## Gutter indicators
|
||||
|
||||
|
|
@ -145,7 +145,6 @@ To summarize, here are some examples of where you can use VS Code as the editor:
|
|||
* [Editing Evolved](/docs/editor/editingevolved.md) - Lint, IntelliSense, Lightbulbs, Peek and Goto Definition and more
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines
|
||||
* [Tasks](/docs/editor/tasks.md) - Running tasks with Gulp, Grunt and Jake. Showing Errors and Warnings
|
||||
* [Customization](/docs/customization/overview.md) - Themes, settings and keyboard bindings
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
@ -194,7 +193,7 @@ Next, assuming you want to remove the unintended repo initialization, look for t
|
|||
You can either:
|
||||
|
||||
* Add the location of `git.exe` to `PATH` and restart VS Code.
|
||||
* Set the `git.path` [setting](/docs/customization/userandworkspace.md) to the location of `git.exe`.
|
||||
* Set the `git.path` [setting](/docs/getstarted/settings.md) to the location of `git.exe`.
|
||||
|
||||
On a **GitHub Desktop** Windows installation, `git.exe` is usually under `C:\Users\USERNAME\AppData\Local\GitHub\PortableGit_COMMITID\ming32\bin`. Searching for `git.exe` under AppData\Local\GitHub should find the binary.
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ Contribute an entry consisting of a title and a command to invoke to the Command
|
|||
|
||||
## contributes.menus
|
||||
|
||||
Contribute a menu item for a command to the editor or Explorer. The menu item definition contains the command that should be invoked when selected and the condition under which the item should show. The latter is defined with the `when` clause which uses the key bindings [when clause contexts](/docs/customization/keybindings.md#when-clause-contexts). In addition to the mandatory `command` property, an alternative command can be defined using the `alt`-property. It will be shown and invoked when pressing `kbstyle(Alt)` while hovering over a menu item. Last, a `group`-property defines sorting and grouping of menu items. The `navigation` group is special as it will always be sorted to the top/beginning of a menu.
|
||||
Contribute a menu item for a command to the editor or Explorer. The menu item definition contains the command that should be invoked when selected and the condition under which the item should show. The latter is defined with the `when` clause which uses the key bindings [when clause contexts](/docs/getstarted/keybindings.md#when-clause-contexts). In addition to the mandatory `command` property, an alternative command can be defined using the `alt`-property. It will be shown and invoked when pressing `kbstyle(Alt)` while hovering over a menu item. Last, a `group`-property defines sorting and grouping of menu items. The `navigation` group is special as it will always be sorted to the top/beginning of a menu.
|
||||
|
||||
Currently extension writers can to contribute to:
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ The order inside a group depends the title or an order-attribute. The group-loca
|
|||
|
||||
## contributes.keybindings
|
||||
|
||||
Contribute a key binding rule defining what command should be invoked when the user presses a key combination. See the [Key Bindings](/docs/customization/keybindings.md) topic where key bindings are explained in detail.
|
||||
Contribute a key binding rule defining what command should be invoked when the user presses a key combination. See the [Key Bindings](/docs/getstarted/keybindings.md) topic where key bindings are explained in detail.
|
||||
|
||||
Contributing a key binding will cause the Default Keyboard Shortcuts to display your rule, and every UI representation of the command will now show the key binding you have added. And, of course, when the user presses the key combination the command will be invoked.
|
||||
|
||||
|
|
@ -355,7 +355,7 @@ Contribute a TextMate grammar to a language. You must provide the `language` thi
|
|||
}
|
||||
```
|
||||
|
||||
See [Adding Language Colorization](/docs/customization/colorizer.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmLanguage files as VS Code extensions.
|
||||
See [Adding Language Colorization](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmLanguage files as VS Code extensions.
|
||||
|
||||
|
||||
|
||||
|
|
@ -377,7 +377,7 @@ Contribute a TextMate theme to VS Code. You must specify a label, whether the th
|
|||
|
||||
|
||||
|
||||
See [Changing the Color Theme](/docs/customization/themes.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmTheme files as VS Code extensions.
|
||||
See [Changing the Color Theme](/docs/extensions/themes-snippets-colorizers.md) for instructions on using the [yo code extension generator](/docs/tools/yocode.md) to quickly package TextMate .tmTheme files as VS Code extensions.
|
||||
|
||||
## contributes.snippets
|
||||
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ In order to support syntax highlighting, your extension needs to registers a Tex
|
|||
|
||||
|
||||
|
||||
With code snippets, you can provide useful source code templates with placeholders. You need to register a file that contains the snippets for your language in your extension's `package.json` file. You can learn about VS Code's snippet schema in [Creating Your Own Snippets](/docs/customization/userdefinedsnippets.md#creating-your-own-snippets).
|
||||
With code snippets, you can provide useful source code templates with placeholders. You need to register a file that contains the snippets for your language in your extension's `package.json` file. You can learn about VS Code's snippet schema in [Creating Your Own Snippets](/docs/editor/userdefinedsnippets.md#creating-your-own-snippets).
|
||||
|
||||
```json
|
||||
"contributes": {
|
||||
|
|
@ -902,7 +902,7 @@ export function activate(ctx: vscode.ExtensionContext): void {
|
|||
|
||||
Provide the user with support for formatting text as they type.
|
||||
|
||||
**Note**: The user [setting](/docs/customization/userandworkspace.md) `editor.formatOnType` controls whether source code gets formatted or not as the user types.
|
||||
**Note**: The user [setting](/docs/getstarted/settings.md) `editor.formatOnType` controls whether source code gets formatted or not as the user types.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ MetaDescription: Learn the details of Visual Studio Code's rich extensibility (p
|
|||
|
||||
This section of our documentation goes into detail on the various features of VS Code extensibility. It's worth reviewing the introduction on the [extensions](/docs/extensions/overview.md) as well as going through the ['Hello World'](/docs/extensions/example-hello-world.md) example before digging in too deeply here.
|
||||
|
||||
The easiest way to see VS Code extensions in action is via the [Extension Marketplace](/docs/editor/extension-gallery.md). Once you have built your first extension or are ready to share a [customization](/docs/customization/overview.md), it can be [published](/docs/tools/vscecli.md) for others to install.
|
||||
The easiest way to see VS Code extensions in action is via the [Extension Marketplace](/docs/editor/extension-gallery.md). Once you have built your first extension, it can be [published](/docs/tools/vscecli.md) for others to install.
|
||||
|
||||
## The Extensibility Reference Documents
|
||||
|
||||
|
|
|
|||
|
|
@ -285,6 +285,5 @@ Read on to find out about:
|
|||
|
||||
* [Yo Code](/docs/tools/yocode.md) - learn about other options in Yo Code
|
||||
* [Extension API](/docs/extensionAPI/overview.md) - Get an overview of the Extension API
|
||||
* [Customization](/docs/customization/overview.md) - Themes, settings and keyboard bindings
|
||||
* [Publishing Tool](/docs/tools/vscecli.md) - Learn how to publish an extension to the public Marketplace
|
||||
* [Editor API](/docs/extensionAPI/vscode-api.md#window) - Learn more about Text Documents, Text Editors and editing text
|
||||
|
|
@ -7,15 +7,12 @@ PageTitle: Extending Visual Studio Code
|
|||
DateApproved: 3/1/2017
|
||||
MetaDescription: Visual Studio Code has a rich extensibility model for interacting with and adding to the tool. Learn how to create your own extensions (plug-ins) for Visual Studio Code.
|
||||
---
|
||||
|
||||
# Extending Visual Studio Code
|
||||
|
||||
If you are interested in extending VS Code, you are in the right place. Here we present an outline of the VS Code extensibility documentation and how to quickly build your first VS Code extension. If you're curious about our design approach to extensibility for VS Code, you can read about it [here](/docs/extensions/our-approach.md).
|
||||
|
||||
If you just want to use existing extensions, see the [Extension Marketplace](/docs/editor/extension-gallery.md) topic where we show you how to find and install extensions from the VS Code [Marketplace](https://marketplace.visualstudio.com/VSCode).
|
||||
|
||||
>**Tip:** Don't forget there are several ways to [customize](/docs/customization/overview.md) VS Code without writing an extension. This includes adding [Themes](/docs/customization/themes.md), [basic Language Support](/docs/customization/colorizer.md), and [Snippets](/docs/customization/userdefinedsnippets.md) without writing a single line of code.
|
||||
|
||||
All VS Code extensions share a common model of contribution (registration), activation (loading) and access to the VS Code extensibility API. There are however two special flavors of VS Code extensions, language servers and debuggers, which have their own additional protocols and are covered in their own sections of the documentation.
|
||||
|
||||
1. [Extensions](/docs/extensions/overview.md#extensions) - the base building block
|
||||
|
|
|
|||
|
|
@ -268,7 +268,7 @@ Central to language support is a TextMate [language specification](https://manua
|
|||
|
||||
A good place to look for existing TextMate .tmLanguage files is on GitHub. Search for a TextMate bundle for the language you are interested in and then navigate to the `Syntaxes` folder. The 'code' Yeoman generator can import either .tmLanguage or .pList files. When prompted for the URL or file location, pass the raw path to the .tmLanguage file e.g. http://raw.githubusercontent.com/textmate/ant.tmbundle/master/Syntaxes/Ant.tmLanguage. Make sure that the path points to the content of the file, not the HTML file showing the content.
|
||||
|
||||
|
||||
|
||||
|
||||
The generator will prompt you for other information such a unique name (this should be unique to avoid clashing with other extensions) and the language name, aliases and file extensions. You also have to provide the top level scope name of the grammar. That scope name must match the scope name in the tmLanguage file.
|
||||
|
||||
|
|
@ -304,7 +304,7 @@ The generated `vsc-extension-quickstart.md` file also contains more information
|
|||
|
||||
To use your extension in your stable VS Code installation, copy the complete output folder to a new folder under [your `.vscode/extensions` folder](/docs/extensions/install-extension.md#your-extensions-folder) and restart VS Code. When you restart VS Code, your new language will be visible in the language specifier dropdown and you'll get full colorization and bracket/tag matching for files matching the language's file extension.
|
||||
|
||||
|
||||
|
||||
|
||||
## Publishing Language Support to the Extension Marketplace
|
||||
|
||||
|
|
@ -316,7 +316,7 @@ We also have recommendations on how to make your extension look great on the VS
|
|||
|
||||
## Add to your Language Support Extension
|
||||
|
||||
When you're adding a new language to VS Code, it is also great to add language [snippets](/docs/customization/userdefinedsnippets.md) to support common editing actions. It is easy to [combine multiple extensions](/docs/extensionAPI/extension-manifest.md#combining-extension-contributions) like snippets and colorizers into the same extension. You can modify the colorizer extension manifest `package.json` to include a `snippets` contribution and the snippets.json.
|
||||
When you're adding a new language to VS Code, it is also great to add language [snippets](/docs/editor/userdefinedsnippets.md) to support common editing actions. It is easy to [combine multiple extensions](/docs/extensionAPI/extension-manifest.md#combining-extension-contributions) like snippets and colorizers into the same extension. You can modify the colorizer extension manifest `package.json` to include a `snippets` contribution and the snippets.json.
|
||||
|
||||
```json
|
||||
{
|
||||
|
|
@ -354,17 +354,15 @@ When you're adding a new language to VS Code, it is also great to add language [
|
|||
|
||||
## Next Steps
|
||||
|
||||
Colorizers are just one way to customize VS Code, If you'd like to learn more about VS Code extensibility, try these topics:
|
||||
If you'd like to learn more about VS Code extensibility, try these topics:
|
||||
|
||||
* [Snippets](/docs/customization/userdefinedsnippets) - Learn how to also include snippets in your language extension.
|
||||
* [Custom themes](/docs/customization/themes.md) - Learn how to import existing TextMate themes.
|
||||
* [Extending Visual Studio Code](/docs/extensions/overview.md) - Learn about other ways to extend VS Code
|
||||
|
||||
## Common Questions
|
||||
|
||||
**Q: What parts of VS code can I theme with a custom color theme?**
|
||||
|
||||
The VS Code color themes affect the editor input area (text foreground, background, selection, lineHighlight, caret, and the syntax tokens) as well as some of the custom UI (see the list in [Creating a Theme](/docs/customization/themes.md#creating-a-custom-theme)). When contributing a theme, you also specify a base theme: light (`vs`), dark (`vs-dark`) and high contrast (`hc-black`). The base theme is used for all other areas in the workbench such as the File Explorer. Base themes are not customizable or contributable by extensions.
|
||||
The VS Code color themes affect the editor input area (text foreground, background, selection, lineHighlight, caret, and the syntax tokens) as well as some of the custom UI (see the list in [Creating a Theme](/docs/extensions/themes-snippets-colorizers.md#creating-a-custom-theme)). When contributing a theme, you also specify a base theme: light (`vs`), dark (`vs-dark`) and high contrast (`hc-black`). The base theme is used for all other areas in the workbench such as the File Explorer. Base themes are not customizable or contributable by extensions.
|
||||
|
||||
**Q: Is there a list of scopes that I can use in my custom color theme?**
|
||||
|
||||
|
|
@ -405,7 +403,7 @@ To learn about what scopes are used where, check out the [TextMate documentation
|
|||
|
||||
**Q: Can I add more file extensions to an existing colorizer?**
|
||||
|
||||
**A:** Yes. To extend an existing colorizer, you can associate a file extension to an existing language identifier with the `files.associations` [setting](/docs/customization/userandworkspace.md). IntelliSense will show you the list of currently available language ids.
|
||||
**A:** Yes. To extend an existing colorizer, you can associate a file extension to an existing language identifier with the `files.associations` [setting](/docs/getstarted/settings.md). IntelliSense will show you the list of currently available language ids.
|
||||
|
||||
For example, the setting below adds the `.mmd` file extension to the `markdown` colorizer:
|
||||
|
||||
|
|
|
|||
|
До Ширина: | Высота: | Размер: 168 KiB После Ширина: | Высота: | Размер: 168 KiB |
|
До Ширина: | Высота: | Размер: 53 KiB После Ширина: | Высота: | Размер: 53 KiB |
|
До Ширина: | Высота: | Размер: 29 KiB После Ширина: | Высота: | Размер: 29 KiB |
|
До Ширина: | Высота: | Размер: 208 KiB После Ширина: | Высота: | Размер: 208 KiB |
|
До Ширина: | Высота: | Размер: 176 KiB После Ширина: | Высота: | Размер: 176 KiB |
|
|
@ -35,7 +35,7 @@ Below are links to the three platform-specific versions:
|
|||
|
||||
## Basic Editing
|
||||
|
||||
>**Note:** The following keys are rendered assuming a standard US keyboard layout. If you use a different keyboard layout, please [read below](/docs/customization/keybindings.md#keyboard-layouts).
|
||||
>**Note:** The following keys are rendered assuming a standard US keyboard layout. If you use a different keyboard layout, please [read below](/docs/getstarted/keybindings.md#keyboard-layouts).
|
||||
|
||||
Key|Command|Command id
|
||||
---|-------|----------
|
||||
|
|
@ -413,10 +413,9 @@ There is also a widget that helps input the key binding rule when editing `keybi
|
|||
|
||||
Now that you know about our Key binding support, what's next...
|
||||
|
||||
* [Customization](/docs/customization/overview.md) - Configure Code the way you want - Themes, Settings and more
|
||||
* [Language Support](/docs/languages/overview.md) - Our Good, Better, Best language grid to see what you can expect
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines
|
||||
* [Node.js](/docs/runtimes/nodejs.md) - End to end Node.js scenario with a sample app
|
||||
* [Node.js](/docs/nodejs/nodejs-tutorial.md) - End to end Node.js scenario with a sample app
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ The menu under **File** > **Preferences** (**Code** > **Preferences** on Mac) pr
|
|||
|
||||
In the example below, we disabled line numbers in the editor and configured line wrapping to wrap automatically based on the size of the editor.
|
||||
|
||||
|
||||
|
||||
|
||||
Changes to settings are reloaded by VS Code after the modified `settings.json` file is saved.
|
||||
|
||||
|
|
@ -49,19 +49,19 @@ When you open settings, we show **Default Settings** to search and discover sett
|
|||
|
||||
Default settings are represented in groups so that you can navigate them easily. It has **Most Commonly Used** group on the top to see the most common customizations done by VS Code users.
|
||||
|
||||
|
||||
|
||||
|
||||
Here is the [copy of default settings](/docs/customization/userandworkspace.md#copy-of-default-settings) that comes with VS Code.
|
||||
Here is the [copy of default settings](/docs/getstarted/settings.md#copy-of-default-settings) that comes with VS Code.
|
||||
|
||||
## Language specific editor settings
|
||||
|
||||
To customize your editor by language, run the global command **Preferences: Configure language specific settings...** (command id: `workbench.action.configureLanguageBasedSettings`) from the **Command Palette** (`kb(workbench.action.showCommands)`) which opens the language picker. Selecting the language you want, opens the Settings editor with the language entry where you can add applicable settings.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
If you have a file open and you want to customize the editor for this file type, click on the Language Mode in the Status Bar to the bottom-right of the VS Code window. This opens the Language Mode picker with an option **Configure 'language_name' language based settings...**. Selecting this opens the Settings editor with the language entry where you can add applicable settings.
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ Color themes let you modify VS Code's background, text, and language syntax colo
|
|||
|
||||
## Selecting the Color Theme
|
||||
|
||||
The current color theme is configured in the [settings](/docs/customization/userandworkspace.md).
|
||||
The current color theme is configured in the [settings](/docs/getstarted/settings.md).
|
||||
|
||||
```javascript
|
||||
// Specifies the color theme used in the workbench.
|
||||
|
|
@ -51,7 +51,7 @@ File icon themes can be contributed by extensions and selected by users as their
|
|||
|
||||
## Selecting the File Icon Theme
|
||||
|
||||
The current File Icon theme is persisted in your user [settings](/docs/customization/userandworkspace.md).
|
||||
The current File Icon theme is persisted in your user [settings](/docs/getstarted/settings.md).
|
||||
|
||||
```javascript
|
||||
// Specifies the icon theme used in the workbench.
|
||||
|
|
@ -76,6 +76,5 @@ You can also browse the [VS Code Marketplace](https://marketplace.visualstudio.c
|
|||
|
||||
Themes are just one way to customize VS Code. If you'd like to learn more about VS Code extensibility, try these topics:
|
||||
|
||||
* [Colorizers and Bracket Matchers](/docs/customization/colorizer.md) - Learn how to import TextMate colorizers
|
||||
* [Snippets](/docs/customization/userdefinedsnippets.md) - Add additional snippets to your favorite language
|
||||
* [Snippets](/docs/editor/userdefinedsnippets.md) - Add additional snippets to your favorite language
|
||||
* [Extending Visual Studio Code](/docs/extensions/overview.md) - Learn about other ways to extend VS Code
|
||||
|
|
@ -33,7 +33,7 @@ Each time you start VS Code, it opens up in the same state it was in when you la
|
|||
|
||||
|
||||
|
||||
VS Code allows up to three visible editors at any one time, allowing you to edit or view up to three files together side by side. The open files in each editor are displayed with tabbed headers (Tabs) at the top of the editor region. To learn more about tabbed headers, see the [Tabs](/docs/editor/tabs.md) topic.
|
||||
VS Code allows up to three visible editors at any one time, allowing you to edit or view up to three files together side by side. The open files in each editor are displayed with tabbed headers (Tabs) at the top of the editor region. To learn more about tabbed headers, see the [Tabs](/docs/getstarted/userinterface.md#tabs) section below.
|
||||
|
||||
>**Tip:** You can move the Side Bar to the right hand side (**View** > **Move Sidebar**) or toggle its visibility (`kb(workbench.action.toggleSidebarVisibility)`).
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ You can also navigate to the location of a file or folder in the native Explorer
|
|||
|
||||
>**Tip:** Type `kb(workbench.action.quickOpen)` (**Quick Open**) to quickly search and open a file by its name.
|
||||
|
||||
By default, VS Code excludes some folders from the explorer (for example. `.git`). Use the `files.exclude` [setting](/docs/customization/userandworkspace.md) to configure rules for hiding files and folders from the explorer.
|
||||
By default, VS Code excludes some folders from the explorer (for example. `.git`). Use the `files.exclude` [setting](/docs/getstarted/settings.md) to configure rules for hiding files and folders from the explorer.
|
||||
|
||||
**Tip:** This is really useful to hide derived resources files, like `\*.meta` in Unity, or `\*.js` in a TypeScript project. For Unity to exclude the `\*.cs.meta` files, the pattern to choose would be: `"**/*.cs.meta": true`. For TypeScript, you can exclude generated JavaScript for TypeScript files with: `"**/*.js": {"when": "$(basename).ts"}`.
|
||||
|
||||
|
|
@ -123,7 +123,7 @@ Type `?` into the input field to get a list of available commands you can execut
|
|||
|
||||
## Configuring the Editor
|
||||
|
||||
VS Code gives you many options to configure the editor. You can set options globally through user settings or per project/folder through workspace settings. Settings values are kept in a `settings.json` [file](/docs/getstarted/userandworkspace.md#settings-file-locations).
|
||||
VS Code gives you many options to configure the editor. You can set options globally through user settings or per project/folder through workspace settings. Settings values are kept in a `settings.json` [file](/docs/getstarted/settings.md#settings-file-locations).
|
||||
|
||||
* Select **File** > **Preferences** > **User Settings** (or press `kb(workbench.action.showCommands)`, type `user` and press `Enter`) to edit the user settings.json file.
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ VS Code gives you many options to configure the editor. You can set options glob
|
|||
|
||||
>**Note for Mac users:** The **Preferences** menu is under **Code** not **File**. For example, **Code** > **Preferences** > **User Settings**.
|
||||
|
||||
You will see the VS Code [Default Settings](/docs/getstarted/userandworkspace.md#default-settings) in the left window and your editable `settings.json` on the right. You can easily filter settings in the `Default Settings` using the search box at the top. Copy a setting over to the editable `settings.json` on the right by clicking on the edit icon after the setting. Settings with a fixed set values allow you to pick a value as part of their edit icon menu.
|
||||
You will see the VS Code [Default Settings](/docs/getstarted/settings.md#default-settings) in the left window and your editable `settings.json` on the right. You can easily filter settings in the `Default Settings` using the search box at the top. Copy a setting over to the editable `settings.json` on the right by clicking on the edit icon after the setting. Settings with a fixed set values allow you to pick a value as part of their edit icon menu.
|
||||
|
||||
After editing your settings, type `kb(workbench.action.files.save)` to save your changes. The changes will take effect immediately.
|
||||
|
||||
|
|
@ -149,7 +149,7 @@ Tabs let you quickly navigate between items and you can Drag and Drop Tabs to re
|
|||
|
||||
When you have more open items than can fit in the title area, you can use the **Show Opened Editors** command (available through the `...` More button) to display a dropdown of tabbed items.
|
||||
|
||||
If you don't want to use Tabs, you can disable the feature by setting the `workbench.editor.showTabs` [setting](/docs/customization/userandworkspace.md) to false:
|
||||
If you don't want to use Tabs, you can disable the feature by setting the `workbench.editor.showTabs` [setting](/docs/getstarted/settings.md) to false:
|
||||
|
||||
```json
|
||||
"workbench.editor.showTabs": false
|
||||
|
|
@ -207,7 +207,7 @@ You can toggle the editor group layout between vertical and horizontal with:
|
|||
|
||||
Here are some handy keyboard shortcuts to quickly navigate between editors and editor groups.
|
||||
|
||||
>If you'd like to modify the default keyboard shortcuts, see [Key Bindings](/docs/customization/keybindings.md) for details.
|
||||
>If you'd like to modify the default keyboard shortcuts, see [Key Bindings](/docs/getstarted/keybindings.md) for details.
|
||||
|
||||
* `kb(workbench.action.nextEditor)` go to the right editor.
|
||||
* `kb(workbench.action.previousEditor)` go to the left editor.
|
||||
|
|
@ -228,13 +228,13 @@ If you prefer not to use Tabs (tabbed headings), you can disable Tabs (tabbed he
|
|||
|
||||
### Disable Preview mode
|
||||
|
||||
Without Tabs, the **OPEN EDITORS** section of the File Explorer is a quick way to do file navigation. With [preview editor mode](/docs/editor/tabs.md#preview-mode), files are not added to the **OPEN EDITOR** list nor editor group on single-click open. You can disable this feature through the `workbench.editor.enablePreview` and `workbench.editor.enablePreviewFromQuickOpen` settings.
|
||||
Without Tabs, the **OPEN EDITORS** section of the File Explorer is a quick way to do file navigation. With [preview editor mode](/docs/getstarted/userinterface.md#preview-mode), files are not added to the **OPEN EDITOR** list nor editor group on single-click open. You can disable this feature through the `workbench.editor.enablePreview` and `workbench.editor.enablePreviewFromQuickOpen` settings.
|
||||
|
||||
### Ctrl+Tab to navigate in entire editor history
|
||||
|
||||
You can change keybindings for `kbstyle(Ctrl+Tab)` to show you a list of all opened editors from the history independent from the active editor group.
|
||||
|
||||
Edit your [keybindings](/docs/customization/keybindings.md) and add the following:
|
||||
Edit your [keybindings](/docs/getstarted/keybindings.md) and add the following:
|
||||
|
||||
```json
|
||||
{ "key": "ctrl+tab", "command": "workbench.action.openPreviousEditorFromHistory" },
|
||||
|
|
@ -243,7 +243,7 @@ Edit your [keybindings](/docs/customization/keybindings.md) and add the followin
|
|||
|
||||
### Close an entire group instead of a single editor
|
||||
|
||||
If you liked the behavior of VS Code closing an entire group when closing one editor, you can bind the following in your [keybindings](/docs/customization/keybindings.md).
|
||||
If you liked the behavior of VS Code closing an entire group when closing one editor, you can bind the following in your [keybindings](/docs/getstarted/keybindings.md).
|
||||
|
||||
Mac:
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ In this tutorial, we walk you through setting up Visual Studio Code and give an
|
|||
|
||||
* [The Basics](/docs/editor/codebasics.md) - View the documentation for the basics of VS Code.
|
||||
* [Setup Overview](/docs/setup/setup-overview.md) - Documentation for getting up and running with VS Code, including platform specific setup.
|
||||
* [Keyboard Shortcuts](/docs/customization/keybindings.md) - Customize your own shortcuts, download a reference sheet, or install a Keymap extension.
|
||||
* [Keyboard Shortcuts](/docs/getstarted/keybindings.md) - Customize your own shortcuts, download a reference sheet, or install a Keymap extension.
|
||||
* [Keymaps in the Marketplace](https://marketplace.visualstudio.com/search?target=VSCode&category=Keymaps&sortBy=Downloads) - Install a Keymap extension to bring the keybindings from your previous editor to VS Code.
|
||||
|
||||
## Next Video
|
||||
|
|
|
|||
|
|
@ -23,10 +23,10 @@ In this tutorial, we show you how to personalize Visual Studio Code.
|
|||
|
||||
## Learn More
|
||||
|
||||
* [User and Workspace Settings](/docs/customization/userandworkspace.md) - Configure user and workspace settings.
|
||||
* [Key Bindings](/docs/customization/keybindings.md) - See the default keyboard shortcuts (key bindings) for editing, navigation, and more.
|
||||
* [Snippets](/docs/customization/userdefinedsnippets.md) - Create your own custom snippets.
|
||||
* [Themes](/docs/customization/themes.md) - Change your Color Theme to customize VS Code's background text and language syntax colorization.
|
||||
* [User and Workspace Settings](/docs/getstarted/settings.md) - Configure user and workspace settings.
|
||||
* [Key Bindings](/docs/getstarted/keybindings.md) - See the default keyboard shortcuts (key bindings) for editing, navigation, and more.
|
||||
* [Snippets](/docs/editor/userdefinedsnippets.md) - Create your own custom snippets.
|
||||
* [Themes](/docs/getstarted/themes.md) - Change your Color Theme to customize VS Code's background text and language syntax colorization.
|
||||
|
||||
## Next Video
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ In this tutorial, we show you how to set up IntelliSense for a JavaScript projec
|
|||
* [IntelliSense](/docs/editor/intellisense.md) - Learn more about IntelliSense and how to use it effectively for your language.
|
||||
* [JavaScript IntelliSense](/docs/languages/javascript.md#intellisense) - Define a JavaScript project with `jsconfig.json` to get IntelliSense across files.
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - Read the official documentation on editing productivity.
|
||||
* [Node.js IntelliSense](/docs/runtimes/nodejs.md#adding-a-jsconfigjson-configuration-file) - Setting up IntelliSense for Node.js.
|
||||
* [Node.js Tutorial](/docs/nodejs/nodejs-tutorial.md) - See IntelliSense in action for Node.js.
|
||||
|
||||
## Next Video
|
||||
|
||||
|
|
|
|||
|
|
@ -79,12 +79,12 @@ If you are debugging with GDB on Windows, see [Windows Debugging on Cygwin/MinGW
|
|||
|
||||
The C/C++ extension for Visual Studio Code supports source code formatting using [clang-format](http://clang.llvm.org/docs/ClangFormat.html) which is included with the extension.
|
||||
|
||||
You can format an entire file with **Format Document** (`kb(editor.action.formatDocument)`) or just the current selection with **Format Selection** (`kb(editor.action.formatSelection)`) in right-click context menu. You can also configure auto-formatting with the following [settings](/docs/customization/userandworkspace.md):
|
||||
You can format an entire file with **Format Document** (`kb(editor.action.formatDocument)`) or just the current selection with **Format Selection** (`kb(editor.action.formatSelection)`) in right-click context menu. You can also configure auto-formatting with the following [settings](/docs/getstarted/settings.md):
|
||||
|
||||
* `C_Cpp.clang_format_formatOnSave` - to format when you save your file.
|
||||
* `editor.formatOnType` - to format as you type (triggered on the `kbstyle(;)` character).
|
||||
|
||||
By default, the clang-format style is set to "file" which means it looks for a `.clang-format` file inside your workspace. If the `.clang-format` file is found, formatting is applied according the settings specified in the file. If no `.clang-format` file is found in your workspace, formatting is applied according to a default style specified in the `C_Cpp.clang_format_fallbackStyle` [setting](/docs/customization/userandworkspace.md) instead. Currently, the default formatting style is "Visual Studio". Using "Visual Studio" formatting ensures that source code formatting will be compatible in both VS Code and Visual Studio Community.
|
||||
By default, the clang-format style is set to "file" which means it looks for a `.clang-format` file inside your workspace. If the `.clang-format` file is found, formatting is applied according the settings specified in the file. If no `.clang-format` file is found in your workspace, formatting is applied according to a default style specified in the `C_Cpp.clang_format_fallbackStyle` [setting](/docs/getstarted/settings.md) instead. Currently, the default formatting style is "Visual Studio". Using "Visual Studio" formatting ensures that source code formatting will be compatible in both VS Code and Visual Studio Community.
|
||||
|
||||
The "Visual Studio" clang-format style is not yet an official OOTB clang-format style but it implies the following clang-format settings:
|
||||
|
||||
|
|
@ -97,7 +97,7 @@ IndentCaseLabels: false
|
|||
ColumnLimit: 0
|
||||
```
|
||||
|
||||
If you'd like to use a different version of clang-format than the one that ships with the extension, you can use the `C_Cpp.clang_format_path` [setting](/docs/customization/userandworkspace.md) and set its value to the path where the clang-format binary is installed.
|
||||
If you'd like to use a different version of clang-format than the one that ships with the extension, you can use the `C_Cpp.clang_format_path` [setting](/docs/getstarted/settings.md) and set its value to the path where the clang-format binary is installed.
|
||||
|
||||
For example on the Windows platform:
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ MetaSocialImage: csharp_languages_csharp.png
|
|||
|
||||
# Working with C#
|
||||
|
||||
The C# support in VS Code is optimized for cross-platform .NET Core development (see [working with .NET Core and VS Code](/docs/runtimes/dotnet.md) for another relevant article). Our focus with VS Code is to be a great editor for cross-platform C# development. For instance, many [Unity](/docs/runtimes/unity.md) game developers enjoy using VS Code in place of the MonoDevelop IDE.
|
||||
The C# support in VS Code is optimized for cross-platform .NET Core development (see [working with .NET Core and VS Code](/docs/other/dotnet.md) for another relevant article). Our focus with VS Code is to be a great editor for cross-platform C# development. For instance, many [Unity](/docs/other/unity.md) game developers enjoy using VS Code in place of the MonoDevelop IDE.
|
||||
|
||||
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ We have several built-in snippets included in VS Code that will come up as you t
|
|||
|
||||
|
||||
|
||||
>**Tip:** You can add in your own User Defined Snippets for C#. Take a look at [User Defined Snippets](/docs/customization/userdefinedsnippets.md) to find out how.
|
||||
>**Tip:** You can add in your own User Defined Snippets for C#. Take a look at [User Defined Snippets](/docs/editor/userdefinedsnippets.md) to find out how.
|
||||
|
||||
## Search for Symbols
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ Another cool feature is the ability to see the number of references to a method
|
|||
|
||||
|
||||
|
||||
>**Tip:** You can turn off references information displayed in CodeLens with the `editor.codeLens` [setting](/docs/customization/userandworkspace.md).
|
||||
>**Tip:** You can turn off references information displayed in CodeLens with the `editor.codeLens` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
## Find References/Peek Definition
|
||||
|
||||
|
|
@ -113,7 +113,7 @@ There are some basic quick fixes supported in VS Code. You will see a lightbulb
|
|||
|
||||
Read on to find out about:
|
||||
|
||||
* [.NET Core Development](/docs/runtimes/dotnet.md) - get up and running with cross-platform .NET
|
||||
* [.NET Core Development](/docs/other/dotnet.md) - get up and running with cross-platform .NET
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - find out more about advanced editing features
|
||||
* [Tasks](/docs/editor/tasks.md) - use tasks to build your project and more
|
||||
* [Debugging](/docs/editor/debugging.md) - find out how to use the debugger with your project
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Press `kb(editor.emmet.action.expandAbbreviation)` to expand the current abbrevi
|
|||
|
||||
>**Tip:** See the CSS section of the [Emmet cheat sheet](http://docs.emmet.io/cheat-sheet) for valid abbreviations.
|
||||
|
||||
If you'd like to use CSS Emmet abbreviations with other languages, you can associate an Emmet syntax profile (such as `css`, `html`) with other languages with the `emmet.syntaxProfiles` [setting](/docs/customization/userandworkspace.md). The setting takes a [language id](/docs/languages/overview.md#language-id) and associates it with an Emmet profile.
|
||||
If you'd like to use CSS Emmet abbreviations with other languages, you can associate an Emmet syntax profile (such as `css`, `html`) with other languages with the `emmet.syntaxProfiles` [setting](/docs/getstarted/settings.md). The setting takes a [language id](/docs/languages/overview.md#language-id) and associates it with an Emmet profile.
|
||||
|
||||
For example, to use Emmet CSS abbreviations inside JavaScript:
|
||||
|
||||
|
|
@ -42,7 +42,7 @@ For example, to use Emmet CSS abbreviations inside JavaScript:
|
|||
}
|
||||
```
|
||||
|
||||
We also support [User Defined Snippets](/docs/customization/userdefinedsnippets.md).
|
||||
We also support [User Defined Snippets](/docs/editor/userdefinedsnippets.md).
|
||||
|
||||
## Syntax coloring & Color preview
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ As you type, we provide syntax highlighting as well as in context preview of col
|
|||
|
||||
|
||||
|
||||
>**Note:** You can hide VS Code's color previews by setting the corresponding `.colorDecorators.enable` [settings](/docs/customization/userandworkspace.md).
|
||||
>**Note:** You can hide VS Code's color previews by setting the corresponding `.colorDecorators.enable` [settings](/docs/getstarted/settings.md).
|
||||
>```json
|
||||
> "css.colorDecorators.enable": false
|
||||
>```
|
||||
|
|
@ -59,7 +59,7 @@ As you type, we provide syntax highlighting as well as in context preview of col
|
|||
|
||||
We support CSS version <= 2.1, Sass version <= 3.2 and Less version <= 2.3.
|
||||
|
||||
>**Note:** You can disable VS Code's default CSS, Sass or Less validation by setting the corresponding `.validate` User or Workspace [setting](/docs/customization/userandworkspace.md) to false.
|
||||
>**Note:** You can disable VS Code's default CSS, Sass or Less validation by setting the corresponding `.validate` User or Workspace [setting](/docs/getstarted/settings.md) to false.
|
||||
>```json
|
||||
> "css.validate": false
|
||||
>```
|
||||
|
|
@ -254,7 +254,7 @@ If you want to stop the task, you can use the **Tasks: Terminate Running Task**
|
|||
|
||||
## Customizing CSS, Sass and Less Settings
|
||||
|
||||
You can configure the following lint warnings as [User and Workspace Settings](/docs/customization/userandworkspace.md).
|
||||
You can configure the following lint warnings as [User and Workspace Settings](/docs/getstarted/settings.md).
|
||||
|
||||
The `validate` setting allows you turn off the built-in validation. You would do this if you rather use a different linter.
|
||||
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ Many of the most common Docker and docker-compose commands are built right into
|
|||
|
||||
## Dockerfile linting
|
||||
|
||||
You can enable linting of Dockerfile files through the `docker.enableLinting` [setting](/docs/customization/userandworkspace.md). The extension uses the [dockerfile_lint](https://github.com/projectatomic/dockerfile_lint) rules based linter to analyze the Dockerfile. You can provide your own customized rules file by using the `docker.linterRuleFile` setting. You can find [more information](https://github.com/projectatomic/dockerfile_lint#extending-and-customizing-rule-files) on how to create rules files as well as [sample rules files](https://github.com/projectatomic/dockerfile_lint/tree/master/sample_rules) in the [dockerfile_lint](https://github.com/projectatomic/dockerfile_lint) project.
|
||||
You can enable linting of Dockerfile files through the `docker.enableLinting` [setting](/docs/getstarted/settings.md). The extension uses the [dockerfile_lint](https://github.com/projectatomic/dockerfile_lint) rules based linter to analyze the Dockerfile. You can provide your own customized rules file by using the `docker.linterRuleFile` setting. You can find [more information](https://github.com/projectatomic/dockerfile_lint#extending-and-customizing-rule-files) on how to create rules files as well as [sample rules files](https://github.com/projectatomic/dockerfile_lint/tree/master/sample_rules) in the [dockerfile_lint](https://github.com/projectatomic/dockerfile_lint) project.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ You can install the Go extension from the VS Code [Marketplace](https://marketpl
|
|||
|
||||
As you type in a Go file, you can see IntelliSense providing you with suggested completions. This even works for members in current, imported, and not yet imported packages. Just type any package name followed by `.`, and you will get suggestions for the corresponding package members.
|
||||
|
||||
By setting `go.autocompleteUnimportedPackages` to `true` in your [settings](/docs/customization/userandworkspace.md), you can also get suggestion for packages that you could import. Select one of these suggestions and an import to the selected package will be added to your file.
|
||||
By setting `go.autocompleteUnimportedPackages` to `true` in your [settings](/docs/getstarted/settings.md), you can also get suggestion for packages that you could import. Select one of these suggestions and an import to the selected package will be added to your file.
|
||||
|
||||
>**Tip**: Use `kb(editor.action.triggerSuggest)` to trigger the suggestions manually.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ You can also work with embedded CSS and JavaScript. However, note that script an
|
|||
|
||||
You can trigger suggestions at any time by pressing `kb(editor.action.triggerSuggest)`.
|
||||
|
||||
You can also control which built-in code completion providers are active. Override these in your user or workspace [settings](/docs/customization/userandworkspace.md) if you prefer not to see the corresponding suggestions.
|
||||
You can also control which built-in code completion providers are active. Override these in your user or workspace [settings](/docs/getstarted/settings.md) if you prefer not to see the corresponding suggestions.
|
||||
|
||||
```json
|
||||
// Configures if the built-in HTML language suggests Angular V1 tags and properties.
|
||||
|
|
@ -66,7 +66,7 @@ To improve the formatting of your HTML source code, press `kb(editor.action.form
|
|||
|
||||
>**Tip:** The formatter does not format the tags listed in the `html.format.unformatted` settings. Embedded JavaScript is formatted unless 'script' tags are excluded.
|
||||
|
||||
>**Tip:** Configure the HTML formatter settings in the [User and Workspace Settings](/docs/customization/userandworkspace.md).
|
||||
>**Tip:** Configure the HTML formatter settings in the [User and Workspace Settings](/docs/getstarted/settings.md).
|
||||
|
||||
## Emmet snippets
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ We support Emmet snippet expansion, simply press `kb(editor.emmet.action.expandA
|
|||
|
||||
>**Tip:** See the HTML section of the [Emmet cheat sheet](http://docs.emmet.io/cheat-sheet) for valid abbreviations.
|
||||
|
||||
If you'd like to use HTML Emmet abbreviations with other languages, you can associate an Emmet syntax profile (such as `html`, `css`) with other languages with the `emmet.syntaxProfiles` [setting](/docs/customization/userandworkspace.md). The setting takes a [language id](/docs/languages/overview.md#language-id) and associates it with an Emmet profile.
|
||||
If you'd like to use HTML Emmet abbreviations with other languages, you can associate an Emmet syntax profile (such as `html`, `css`) with other languages with the `emmet.syntaxProfiles` [setting](/docs/getstarted/settings.md). The setting takes a [language id](/docs/languages/overview.md#language-id) and associates it with an Emmet profile.
|
||||
|
||||
For example, to use Emmet HTML abbreviations inside JavaScript:
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ For example, to use Emmet HTML abbreviations inside JavaScript:
|
|||
}
|
||||
```
|
||||
|
||||
We also support [User Defined Snippets](/docs/customization/userdefinedsnippets.md).
|
||||
We also support [User Defined Snippets](/docs/editor/userdefinedsnippets.md).
|
||||
|
||||
## Next Steps
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ For the details of how JavaScript IntelliSense works, including being based on t
|
|||
|
||||
When type inference does not provide the desired information, type information may be provided explicitly with JSDoc annotations. This document describes the [JSDoc annotations](https://github.com/Microsoft/TypeScript/wiki/JsDoc-support-in-JavaScript) currently supported. In addition to objects, methods, and properties, the JavaScript IntelliSense window also provides basic word completion for the symbols in your file.
|
||||
|
||||
VS Code ships with the most stable version of the JavaScript language service. The same language service powers both JavaScript and TypeScript, so if you want to use a newer version, you can define the `typescript.tsdk` [setting](/docs/customization/userandworkspace.md) to point to a directory containing the TypeScript `tsserver.js` file. See more details [here](/docs/languages/typescript.md#using-newer-typescript-versions).
|
||||
VS Code ships with the most stable version of the JavaScript language service. The same language service powers both JavaScript and TypeScript, so if you want to use a newer version, you can define the `typescript.tsdk` [setting](/docs/getstarted/settings.md) to point to a directory containing the TypeScript `tsserver.js` file. See more details [here](/docs/languages/typescript.md#using-newer-typescript-versions).
|
||||
|
||||
## Automatic Type Acquisition
|
||||
|
||||
|
|
@ -124,7 +124,7 @@ You can debug your client side code using a browser debugger such as [Debugger f
|
|||
|
||||
### Debug Server Side
|
||||
|
||||
Debug Node.js in VS Code using the built-in debugger. Setup is easy and you can read a walk-through for Node.js debugging [here](/docs/runtimes/nodejs.md#debugging-your-express-application).
|
||||
Debug Node.js in VS Code using the built-in debugger. Setup is easy and you can read a tutorial for Node.js debugging [here](/docs/nodejs/nodejs-tutorial.md#debugging-your-express-application).
|
||||
|
||||
|
||||
|
||||
|
|
@ -150,7 +150,7 @@ A linter extension may require an external tool. The steps below show how to set
|
|||
|
||||
>**Tip:** You get IntelliSense and hovering inside the `.eslintrc.json` file.
|
||||
|
||||
>**Tip:** The linter is enabled after installation. You can disable a linter with the corresponding `.enable` [setting](/docs/customization/userandworkspace.md). For ESLint, this would be setting `"eslint.enable" : false`.
|
||||
>**Tip:** The linter is enabled after installation. You can disable a linter with the corresponding `.enable` [setting](/docs/getstarted/settings.md). For ESLint, this would be setting `"eslint.enable" : false`.
|
||||
|
||||
It is recommended that you enable the linter rules that warn about undefined and unused variables. To do this, put the following options in your `.eslintrc.json` file.
|
||||
|
||||
|
|
@ -173,9 +173,9 @@ VS Code has several built-in snippets that will come up as you type or you can p
|
|||
|
||||
|
||||
|
||||
> **Tip:** You can add in your own snippets for JavaScript. See [User Defined Snippets](/docs/customization/userdefinedsnippets.md) to find out how.
|
||||
> **Tip:** You can add in your own snippets for JavaScript. See [User Defined Snippets](/docs/editor/userdefinedsnippets.md) to find out how.
|
||||
|
||||
You may not want to show snippets. You can disable them by setting `editor.snippetSuggestions` to `"none"` in your [settings](/docs/customization/userandworkspace.md) file. If you'd like to see snippets, you can specify the order relative to suggestions; at the top (`"top"`), at the bottom (`"bottom"`), or inlined ordered alphabetically (`"inline"`). The default is `"inline"`.
|
||||
You may not want to show snippets. You can disable them by setting `editor.snippetSuggestions` to `"none"` in your [settings](/docs/getstarted/settings.md) file. If you'd like to see snippets, you can specify the order relative to suggestions; at the top (`"top"`), at the bottom (`"bottom"`), or inlined ordered alphabetically (`"inline"`). The default is `"inline"`.
|
||||
|
||||
You can enable tab completions with `editor.tabCompletion` setting. After typing the prefix of a snippet, press `kbstyle(Tab)` to insert it.
|
||||
|
||||
|
|
@ -220,7 +220,7 @@ As with other languages, you can format your JavaScript code in VS Code.
|
|||
|
||||
|
||||
|
||||
VS Code provides several formatting settings for JavaScript. They can all be found in the `javascript.format` [settings](/docs/customization/userandworkspace.md) namespace.
|
||||
VS Code provides several formatting settings for JavaScript. They can all be found in the `javascript.format` [settings](/docs/getstarted/settings.md) namespace.
|
||||
|
||||
```typescript
|
||||
// Defines space handling after a comma delimiter
|
||||
|
|
@ -266,7 +266,7 @@ Read on to find out about:
|
|||
* [jsconfig.json](/docs/languages/jsconfig.md) - Detailed description of the `jsconfig.json` project file.
|
||||
* [IntelliSense](/docs/editor/intellisense.md) - Learn more about IntelliSense and how to use it effectively for your language.
|
||||
* [Debugging](/docs/editor/debugging.md) - Learn how to set up debugging for your application.
|
||||
* [Node.js](/docs/runtimes/nodejs.md) - A walkthrough to create an Express Node.js application.
|
||||
* [Node.js](/docs/nodejs/nodejs-tutorial.md) - A walkthrough to create an Express Node.js application.
|
||||
* [TypeScript](/docs/languages/typescript.md) - VS Code has great support for TypeScript which brings structure and strong typing to your JavaScript code.
|
||||
|
||||
Watch these introductory videos:
|
||||
|
|
@ -309,11 +309,11 @@ When you want to use ES6 style imports but the typings do not yet use ES6 style
|
|||
|
||||
**Q: Can I debug minified/uglified JavaScript?**
|
||||
|
||||
**A:** Yes, you can. You can see this working using JavaScript source maps in the [Node.js Debugging](/docs/editor/node-debugging.md) topic.
|
||||
**A:** Yes, you can. You can see this working using JavaScript source maps in the [Node.js Debugging](/docs/nodejs/nodejs-debugging.md) topic.
|
||||
|
||||
**Q: How do I disable Syntax Validation when using non ES6 constructs?**
|
||||
|
||||
**A:** Some users want to use syntax constructs like the proposed Object Rest/Spread Properties. However, these are currently not supported by VS Code's JavaScript language service and are flagged as errors. For users who still want to use these future features, we provide the `javascript.validate.enable` [setting](/docs/customization/userandworkspace.md).
|
||||
**A:** Some users want to use syntax constructs like the proposed Object Rest/Spread Properties. However, these are currently not supported by VS Code's JavaScript language service and are flagged as errors. For users who still want to use these future features, we provide the `javascript.validate.enable` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
With `javascript.validate.enable: false`, you disable all built-in syntax checking. If you do this, we recommend that you use a linter like [ESLint](http://eslint.org) to validate your source code. Since VS Code's JavaScript support doesn't understand ES7 constructs, features like IntelliSense might not be fully accurate.
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ To understand the structure of JSON files, we use [JSON schemas](http://spacetel
|
|||
|
||||
Servers like [JSON Schema Store](http://schemastore.org) provide schemas for most of the common JSON based configuration files. However, schemas can also be defined in a file in the VS Code workspace, as well as the VS Code settings files.
|
||||
|
||||
The association of a JSON file to a schema can be done either in the JSON file itself using the `$schema` attribute, or in the User or Workspace [Settings](/docs/customization/userandworkspace.md) (**File** > **Preferences** > **User Settings** or **Workspace Settings**) under the property `json.schemas`.
|
||||
The association of a JSON file to a schema can be done either in the JSON file itself using the `$schema` attribute, or in the User or Workspace [Settings](/docs/getstarted/settings.md) (**File** > **Preferences** > **User Settings** or **Workspace Settings**) under the property `json.schemas`.
|
||||
|
||||
VS Code extensions can also define schemas and schema mapping. That's why VS Code already knows about the schema of some well known JSON files such as `package.json`, `bower.json` and `tsconfig.json`.
|
||||
|
||||
|
|
@ -82,7 +82,7 @@ The following excerpt from the User Settings shows how `.babelrc` files are mapp
|
|||
|
||||
>**Tip:** Additionally to defining a schema for `.babelrc`, also make sure that `.babelrc` is associated to the JSON language mode. This is also done in the settings using the `files.association` array setting.
|
||||
|
||||
>**Tip:** For an overview on settings, see [User and Workspace Settings](/docs/customization/userandworkspace.md).
|
||||
>**Tip:** For an overview on settings, see [User and Workspace Settings](/docs/getstarted/settings.md).
|
||||
|
||||
### Mapping to a Schema in the Workspace
|
||||
|
||||
|
|
@ -167,9 +167,3 @@ In addition, you can install an extension for greater functionality.
|
|||
<div class="marketplace-extensions-json"></div>
|
||||
|
||||
> Tip: The extensions shown above are dynamically queried. Click on an extension tile above to read the description and reviews to decide which extension is best for you. See more in the [Marketplace](https://marketplace.visualstudio.com).
|
||||
|
||||
## Next Steps
|
||||
|
||||
Read on to find out about:
|
||||
|
||||
* [Customization](/docs/customization/overview.md) - Customize VS Code to work the way you want
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ When working with a Markdown preview to the side of your editor, VS Code can syn
|
|||
|
||||
|
||||
|
||||
This behavior can be disabled using the `markdown.preview.scrollPreviewWithEditorSelection` [setting](/docs/customization/userandworkspace.md).
|
||||
This behavior can be disabled using the `markdown.preview.scrollPreviewWithEditorSelection` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
The currently selected line is indicated in the Markdown preview by a light gray bar in the left margin:
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ Also, when the Markdown preview is scrolled, the editor will scroll along with i
|
|||
|
||||
|
||||
|
||||
This can be disabled using the `markdown.preview.scrollEditorWithPreview` [setting](/docs/customization/userandworkspace.md).
|
||||
This can be disabled using the `markdown.preview.scrollEditorWithPreview` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
Additionally, double clicking an element in the Markdown preview will automatically open the editor for the file and scroll to the line nearest the clicked element.
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Additionally, double clicking an element in the Markdown preview will automatica
|
|||
|
||||
## Using your own CSS
|
||||
|
||||
By default, we use a CSS style for the preview that matches the style of VS Code. If you want to use your own CSS for the Markdown preview, update the `"markdown.styles": []` [setting](/docs/customization/userandworkspace.md) with the comma-separated list of URL(s) for your style sheet(s).
|
||||
By default, we use a CSS style for the preview that matches the style of VS Code. If you want to use your own CSS for the Markdown preview, update the `"markdown.styles": []` [setting](/docs/getstarted/settings.md) with the comma-separated list of URL(s) for your style sheet(s).
|
||||
|
||||
For instance, in the screen shot above we used a custom CSS that changes the default font for the page and changes the color for the H1 title.
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ Use **File** > **Preferences** > **Workspace Settings** to bring up the workspac
|
|||
|
||||
There are several built-in Markdown snippets included in VS Code - press `kb(editor.action.triggerSuggest)` (Trigger Suggest) and you get a context specific list of suggestions.
|
||||
|
||||
>**Tip:** You can add in your own User Defined Snippets for Markdown. Take a look at [User Defined Snippets](/docs/customization/userdefinedsnippets.md) to find out how.
|
||||
>**Tip:** You can add in your own User Defined Snippets for Markdown. Take a look at [User Defined Snippets](/docs/editor/userdefinedsnippets.md) to find out how.
|
||||
|
||||
## Compiling Markdown into HTML
|
||||
|
||||
|
|
@ -248,10 +248,8 @@ If you want to stop the task, you can use the **Tasks: Terminate Running Task**
|
|||
|
||||
Read on to find out about:
|
||||
|
||||
* [Customization](/docs/customization/overview.md) - Dig into additional settings such as word wrap and User Defined Snippets.
|
||||
* [CSS, Less and Sass](/docs/languages/css.md) - Want to edit your CSS? VS Code has great support for CSS, Less and Sass editing.
|
||||
|
||||
|
||||
## Common Questions
|
||||
|
||||
**Q: Is there spell checking?**
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ You can see the list of currently installed languages and their identifiers in t
|
|||
|
||||
## Adding a file extension to a Language
|
||||
|
||||
You can add new file extensions to an existing language with the `files.associations` [setting](/docs/customization/userandworkspace.md).
|
||||
You can add new file extensions to an existing language with the `files.associations` [setting](/docs/getstarted/settings.md).
|
||||
|
||||
For example, the setting below adds the `.myphp` file extension to the `php` language identifier:
|
||||
|
||||
|
|
@ -82,9 +82,8 @@ IntelliSense (`kb(editor.action.triggerSuggest)`) will show you the available la
|
|||
|
||||
Now you know that VS Code has support for the languages you care about. Read on...
|
||||
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - Lint, IntelliSense, Lightbulbs, Peek and Go to Definition and more
|
||||
* [Code Navigation](/docs/editor/editingevolved.md) - Peek and Go to Definition and more
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines
|
||||
* [Customization](/docs/customization/overview.md) - themes, settings and keyboard bindings
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
@ -94,11 +93,11 @@ Now you know that VS Code has support for the languages you care about. Read on.
|
|||
|
||||
**Q: What if I don't want to create a full language service, can I reuse existing TextMate bundles?**
|
||||
|
||||
**A:** Yes, you can also add support for your favorite language through TextMate colorizers. See [Colorizers](/docs/customization/colorizer.md) to learn how to integrate TextMate .tmLanguage syntax files into VS Code.
|
||||
**A:** Yes, you can also add support for your favorite language through TextMate colorizers. See [Colorizers](/docs/extensions/thmemes-snippets-colorizers.md) to learn how to integrate TextMate .tmLanguage syntax files into VS Code.
|
||||
|
||||
**Q: Can I map additional file extensions to a language?**
|
||||
|
||||
**A:** Yes, with the `files.associations` [setting](/docs/customization/userandworkspace.md) you can map file extensions to an existing language either globally or per workspace.
|
||||
**A:** Yes, with the `files.associations` [setting](/docs/getstarted/settings.md) you can map file extensions to an existing language either globally or per workspace.
|
||||
|
||||
Here is an example that will associate more file extensions to the PHP language:
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ There are many PHP language extensions available on the [VS Code Marketplace](ht
|
|||
|
||||
> Tip: The extensions shown above are dynamically queried. Click on an extension tile above to read the description and reviews to decide which extension is best for you. See more in the [Marketplace](https://marketplace.visualstudio.com).
|
||||
|
||||
> Tip: The following [setting](/docs/customization/userandworkspace.md) allows to disable the built-in PHP completions in favor of proposals created by installed PHP extensions.
|
||||
> Tip: The following [setting](/docs/getstarted/settings.md) allows to disable the built-in PHP completions in favor of proposals created by installed PHP extensions.
|
||||
|
||||
- `php.suggest.basic`: Configures if the built-in PHP language suggestions are enabled. Enabled by default.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ Visual Studio Code includes a set of common snippets for PHP. To access these,
|
|||
|
||||
VS Code uses the official PHP linter (`php -l`) for PHP language diagnostics. This allows VS Code to stay current with PHP linter improvements.
|
||||
|
||||
There are three [settings](/docs/customization/userandworkspace.md) to control the PHP linter:
|
||||
There are three [settings](/docs/getstarted/settings.md) to control the PHP linter:
|
||||
|
||||
* `php.validate.enable`: controls whether to enable PHP linting at all. Enabled by default.
|
||||
* `php.validate.executablePath`: points to the PHP executable on disk. Set this if the PHP executable is not on the system path.
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ No more `print` statement debugging! Set breakpoints, inspect data, and use the
|
|||
|
||||
## Snippets
|
||||
|
||||
Snippets will take productivity to the next level. You can configure [your own snippets](/docs/customization/userdefinedsnippets.md) and use snippets provided by an extension.
|
||||
Snippets will take productivity to the next level. You can configure [your own snippets](/docs/editor/userdefinedsnippets.md) and use snippets provided by an extension.
|
||||
|
||||
<video id="python-snippets-video" src="https://az754404.vo.msecnd.net/public/python-snippets.mp4" poster="/images/python_python-snippets-placeholder.png" autoplay loop controls muted></video>
|
||||
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ If you have [Node.js](https://nodejs.org) installed, you can run your simple Hel
|
|||
node HelloWorld.js
|
||||
```
|
||||
|
||||
> **Tip:** You can also run the program using VS Code's Run/Debug feature. Details about running and debugging node apps in VS Code can be found [here](/docs/runtimes/nodejs#_debugging-your-node-application)
|
||||
> **Tip:** You can also run the program using VS Code's Run/Debug feature. Details about running and debugging node apps in VS Code can be found [here](/docs/nodejs/nodejs-tutorial.md#debugging-your-node-application)
|
||||
|
||||
### Step 4: Reviewing Build Issues
|
||||
|
||||
|
|
@ -153,7 +153,7 @@ If generated (transpiled) JavaScript files do not live next to their source, you
|
|||
|
||||
## Hiding Derived JavaScript Files
|
||||
|
||||
When you are working with TypeScript, you often don’t want to see generated JavaScript files in the explorer or in search results. VS Code offers filtering capabilities with a `files.exclude` [setting](/docs/customization/userandworkspace.md) (**File** > **Preferences** > **Workspace Settings**) and you can easily create an expression to hide those derived files:
|
||||
When you are working with TypeScript, you often don’t want to see generated JavaScript files in the explorer or in search results. VS Code offers filtering capabilities with a `files.exclude` [setting](/docs/getstarted/settings.md) (**File** > **Preferences** > **Workspace Settings**) and you can easily create an expression to hide those derived files:
|
||||
|
||||
`"**/*.js": { "when": "$(basename).ts"}`
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Chakra | all | not yet
|
|||
Although it appears to be possible that the VS Code Node.js debugger picks the best protocol always automatically,
|
||||
we've decided for a 'pessimistic approach' with an explicit launch configuration attribute `protocol` and the following values:
|
||||
|
||||
- **`auto`**: tries to automatically detect the protocol used by the targeted runtime. For configurations of request type `launch` and if no `runtimeExecutable` is specified, we try to determine the version by running node from the PATH with an `--version` argument. If the version is >= 6.9 the new 'inspector' protocol is used. For configurations of request type 'attach' we try to connect with the new protocol and if this works, we use the 'inspector' protocol. We only switch to the new inspector protocol for versions >= 6.9 because of severe problems in earlier versions.
|
||||
- **`auto`**: tries to automatically detect the protocol used by the targeted runtime. For configurations of request type `launch` and if no `runtimeExecutable` is specified, we try to determine the version by running node from the PATH with an `--version` argument. If the version is >= 6.9 the new 'inspector' protocol is used. For configurations of request type 'attach' we try to connect with the new protocol and if this works, we use the 'inspector' protocol. We only switch to the new 'inspector' protocol for versions >= 6.9 because of severe problems in earlier versions.
|
||||
- **`inspector`**: forces the node debugger to use the 'inspector' protocol based implementation. This is supported by node versions >= 6.3, but not (yet) by Electron.
|
||||
- **`legacy`**: forces the node debugger to use the 'legacy' protocol based implementation. This is supported by node versions < v8.0) and Electron.
|
||||
|
||||
|
|
@ -426,7 +426,7 @@ Here are some things to try when your breakpoints turn gray:
|
|||
* Do you have `"sourceMaps": false` in your `launch.json`?
|
||||
* Did you build with source maps enabled? Are there `.js.map` files, or inlined source maps in your `.js` files?
|
||||
* Did you set the `outFiles` property in your `launch.json`? It should be a glob pattern for an absolute path that matches your `.js` files.
|
||||
* Try the new [Inspector Protocol](/docs/editor/node-debugging.md#debugging-with-inspector-protocol) implementation. It can handle some more of the more complex source map cases.
|
||||
* Try the new 'inspector' protocol implementation. It can handle some more of the more complex source map cases.
|
||||
* Are the `sourceRoot` and `sources` properties in your source map correct? Can they be combined to get the correct path to the `.ts` file?
|
||||
* Are you using Webpack? By default, it outputs paths with a `webpack:///` prefix, which the debug adapter can't resolve. You can change this in your Webpack configuration with the `devtoolModuleFilenameTemplate` option, or try using the 'inspector' protocol, which provides some extra options for resolving these paths.
|
||||
* Have you opened the folder in VS Code with the incorrect case? It's possible to open folder `foo/` from the command line like `code FOO` in which case source maps may not be resolved correctly.
|
||||
|
|
@ -437,7 +437,7 @@ Here are some things to try when your breakpoints turn gray:
|
|||
|
||||
In case you didn't already read the Node.js section, take a look at:
|
||||
|
||||
* [Node.js](/docs/runtimes/nodejs.md) - End to end Node scenario with a sample application
|
||||
* [Node.js](/docs/nodejs/nodejs-tutorial.md) - End to end Node scenario with a sample application
|
||||
|
||||
To see a tutorial on the basics of Node.js debugging, check out:
|
||||
|
||||
|
|
|
|||
|
|
@ -287,7 +287,7 @@ Here are some popular extensions from the [Marketplace](https://marketplace.visu
|
|||
|
||||
There is much more to explore with Visual Studio Code, please try the following topics:
|
||||
|
||||
* [Settings](/docs/customization/userandworkspace.md) - Learn how to customize VS Code for how you like to work.
|
||||
* [Settings](/docs/getstarted/settings.md) - Learn how to customize VS Code for how you like to work.
|
||||
* [Debugging](/docs/editor/debugging.md) - This is where VS Code really shines
|
||||
* [Editing Evolved](/docs/editor/editingevolved.md) - Lint, IntelliSense, Lightbulbs, Peek and Go to Definition and more
|
||||
* [Tasks](/docs/editor/tasks.md) - Running tasks with Gulp, Grunt and Jake. Showing Errors and Warnings
|
||||
|
|
@ -108,22 +108,15 @@ To install an Add-in within an Office application, select the **Insert** tab and
|
|||
|
||||
Using the Office Add-ins dialog you can select Add-ins you've uploaded to your Office 365 tenancy's App Catalog (*listed under My Organization*) or acquire Add-ins from the Office Store.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Next Steps
|
||||
|
||||
Check out the other pages on the VS Code site to find out how you can leverage more capabilities of the editor when creating custom Office Add-ins:
|
||||
|
||||
- [Language Overview](/docs/languages/overview.md) - You can write Office Add-ins in many languages. Find out what VS Code has to offer.
|
||||
- [The Basics](/docs/editor/codebasics.md) - Just starting out with VS Code? This is worth reviewing.
|
||||
- [Editing Evolved](/docs/editor/editingevolved.md) - Review all the ways VS Code can help you in editing.
|
||||
- [Node.js](/docs/Runtimes/nodejs.md) - Find out more about our Node.js support.
|
||||
|
||||
|
||||
|
||||
## Common Questions
|
||||
|
||||
**Q: Can I create an Office Add-in with the generator and use VS Code regardless of the language or client-side framework?**
|
||||
|
||||
**A:** Yes, you can. You can use pure HTML, Angular, Ember, React, Aurelia... anything you like!
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ To configure Unity to pass this data to VS Code, set the Editor Args to be `. -g
|
|||
|
||||
**A:** Unity creates a number of additional files that can clutter your workspace in VS Code. You can easily hide these so that you can focus on the files you actually want to edit.
|
||||
|
||||
To do this, add the following JSON to your [workspace settings](/docs/customization/userandworkspace.md).
|
||||
To do this, add the following JSON to your [workspace settings](/docs/getstarted/settings.md).
|
||||
|
||||
```json
|
||||
// Configure glob patterns for excluding files and folders.
|
||||
|
|
|
|||
|
|
@ -49,5 +49,5 @@ Visual Studio Code integrates with existing tool chains. We think the following
|
|||
## Next Steps
|
||||
|
||||
* [The Basics](/docs/editor/codebasics.md) - A quick orientation around VS Code.
|
||||
* [User/Workspace Settings](/docs/customization/userandworkspace.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
* [User/Workspace Settings](/docs/getstarted/settings.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
* [Languages](/docs/languages/overview.md) - VS Code supports many programming languages out-of-the-box as well as many more through community created extensions.
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ Node.js is a popular platform and runtime for easily building and running JavaSc
|
|||
|
||||
If you'd like to install Node.js on Linux, see [Installing Node.js via package manager](https://nodejs.org/en/download/package-manager) to find the Node.js package and installation instructions tailored to your Linux distribution.
|
||||
|
||||
To learn more about JavaScript and Node.js, see our [Node.js walkthrough](/docs/runtimes/nodejs.md) where you'll learn about running and debugging Node.js applications with VS Code.
|
||||
To learn more about JavaScript and Node.js, see our [Node.js tutorial](/docs/nodejs/nodejs-tutorial.md) where you'll learn about running and debugging Node.js applications with VS Code.
|
||||
|
||||
## Setting VS Code as the default text editor
|
||||
|
||||
|
|
@ -115,7 +115,7 @@ Once you have installed VS Code, these topics will help you learn more about VS
|
|||
|
||||
* [Additional Components](/docs/setup/additional-components.md) - Learn how to install Git, Node.js, TypeScript and tools like Yeoman.
|
||||
* [The Basics](/docs/editor/codebasics.md) - A quick orientation around VS Code.
|
||||
* [User/Workspace Settings](/docs/customization/userandworkspace.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
* [User/Workspace Settings](/docs/getstarted/settings.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ VS Code ships monthly [releases](/updates) and supports auto-update when a new r
|
|||
|
||||
## Preferences Menu
|
||||
|
||||
You can configure VS Code through [settings](/docs/customization/userandworkspace.md), [color themes](/docs/customization/themes.md) and [custom keybindings](/docs/customization/keybindings.md) and you will often see mention in our documentation of the **File** > **Preferences** menu group. On a Mac, the **Preferences** menu group is under **Code**, not **File**.
|
||||
You can configure VS Code through [settings](/docs/getstarted/settings.md), [color themes](/docs/getstarted/themes.md) and [custom keybindings](/docs/getstarted/keybindings.md) and you will often see mention in our documentation of the **File** > **Preferences** menu group. On a Mac, the **Preferences** menu group is under **Code**, not **File**.
|
||||
|
||||
## Next Steps
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ Once you have installed VS Code, these topics will help you learn more about VS
|
|||
|
||||
* [Additional Components](/docs/setup/additional-components.md) - Learn how to install Git, Node.js, TypeScript and tools like Yeoman.
|
||||
* [The Basics](/docs/editor/codebasics.md) - A quick orientation around VS Code.
|
||||
* [User/Workspace Settings](/docs/customization/userandworkspace.md) - Learn how to configure VS Code to your preferences settings.
|
||||
* [User/Workspace Settings](/docs/getstarted/settings.md) - Learn how to configure VS Code to your preferences settings.
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ If you work on a machine where Internet traffic needs to go through a proxy serv
|
|||
SET http_proxy=http://10.203.0.1:5187/
|
||||
```
|
||||
|
||||
* Configure the ‘http.proxy’ setting in your user [settings](/docs/customization/userandworkspace.md) (**File** > **Preferences** > **User Settings** or **Code** > **Preferences** > **User Settings** on Mac):
|
||||
* Configure the ‘http.proxy’ setting in your user [settings](/docs/getstarted/settings.md) (**File** > **Preferences** > **User Settings** or **Code** > **Preferences** > **User Settings** on Mac):
|
||||
|
||||
```json
|
||||
"http.proxy": "http://10.203.0.1:5187/"
|
||||
|
|
@ -77,7 +77,7 @@ Once you have installed and set up VS Code, these topics will help you learn mor
|
|||
* [Editing Evolved](/docs/editor/editingevolved.md) - Lint, IntelliSense, Lightbulbs, Peek and Go To Definition and more
|
||||
* [Debugging](/docs/editor/debugging.md) - Debug your source code directly in the VS Code editor.
|
||||
|
||||
If you'd like to getting something running quickly, try the [Node.js runtime](/docs/runtimes/nodejs.md) walkthrough which will have you debugging a Node.js web application with VS Code in minutes.
|
||||
If you'd like to getting something running quickly, try the [Node.js tutorial](/docs/nodejs/nodejs-tutorial.md) walkthrough which will have you debugging a Node.js web application with VS Code in minutes.
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Once you have installed VS Code, these topics will help you learn more about VS
|
|||
|
||||
* [Additional Components](/docs/setup/additional-components.md) - Learn how to install Git, Node.js, TypeScript and tools like Yeoman.
|
||||
* [The Basics](/docs/editor/codebasics.md) - A quick orientation around VS Code.
|
||||
* [User/Workspace Settings](/docs/customization/userandworkspace.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
* [User/Workspace Settings](/docs/getstarted/settings.md) - Learn how to configure VS Code to your preferences through settings.
|
||||
|
||||
## Common Questions
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ The integrated terminal had several changes related to polish and compatibility
|
|||
|
||||
|
||||
|
||||
- **Copy and paste support on Windows and Linux**: Proper copy and paste support has arrived for Windows and Linux within the terminal. The default keybindings are `kb(workbench.action.terminal.copySelection)` and `kb(workbench.action.terminal.paste)` respectively. Note that these command keybindings are not assigned by default on Mac but you can easily add [your own keybindings](/docs/customization/keybindings.md).
|
||||
- **Copy and paste support on Windows and Linux**: Proper copy and paste support has arrived for Windows and Linux within the terminal. The default keybindings are `kb(workbench.action.terminal.copySelection)` and `kb(workbench.action.terminal.paste)` respectively. Note that these command keybindings are not assigned by default on Mac but you can easily add [your own keybindings](/docs/getstarted/keybindings.md).
|
||||
- **Context menu**: A right-click context menu has been added with the options **New Terminal**, **Copy** and **Paste**.
|
||||
- **Accessibility**: It's now possible to escape focus in the terminal by pressing `kb(editor.action.toggleTabFocusMode)` to enable `kbstyle(Tab)` focus mode, just like in the editor. When this mode is enabled, `kbstyle(Tab)` and `kbstyle(Shift+Tab)` will not be passed to the terminal but instead change the element that is being focused.
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ The shell that is used defaults to `$SHELL` on Linux and OS X, and `%COMSPEC%` o
|
|||
|
||||
Please note, this is an early version of what we want to deliver. Currently VS Code only supports a single terminal and there still are missing features like copying and pasting with the keyboard. Windows 10 users may experience problems getting `cmd.exe` to work. If so, please try enabling the legacy terminal as described in [#143](https://github.com/Microsoft/vscode/issues/143#issuecomment-221054202). The full list of current bugs and feature requests can be found [here](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Aintegrated-terminal).
|
||||
|
||||
>**Note:** The **Toggle Integrated Terminal** key binding `kb(workbench.action.terminal.toggleTerminal)` had previously been bound to the **Cycle Between Open Editors** command. You can [customize](https://code.visualstudio.com/docs/customization/keybindings#_customizing-shortcuts) the key bindings and change the behavior back if desired.
|
||||
>**Note:** The **Toggle Integrated Terminal** key binding `kb(workbench.action.terminal.toggleTerminal)` had previously been bound to the **Cycle Between Open Editors** command. You can [customize](https://code.visualstudio.com/docs/getstarted/keybindings#_customizing-shortcuts) the key bindings and change the behavior back if desired.
|
||||
|
||||
### Removing a specific key binding rule
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ See [how to update](/docs/supporting/howtoupdate.md) to get the bits. Read on fo
|
|||
|
||||
## Key Bindings
|
||||
|
||||
Based on user feedback (thanks!) we've decided to make some key binding changes. If you do not like our changes, you can always change key bindings as described in the [keybindings](/docs/customization/keybindings.md) documentation.
|
||||
Based on user feedback (thanks!) we've decided to make some key binding changes. If you do not like our changes, you can always change key bindings as described in the [keybindings](/docs/getstarted/keybindings.md) documentation.
|
||||
|
||||
* The native File Open dialog has been restored to `kb(workbench.action.files.openFile)`. We received strong feedback that using this key for the Code File Open dialog is confusing.
|
||||
* The Code File Open dialog is now accessible via `kb(workbench.action.quickOpen)`. We needed to find a new key for the Code File Open dialog. Since many editors are now using `kb(workbench.action.quickOpen)` for their enriched File Open dialog, we decided to go with this trend.
|
||||
|
|
|
|||
|
|
@ -146,7 +146,7 @@ We improved colorization for shebang `#!`, as shown in the first line here:
|
|||
|
||||
## Snippets
|
||||
|
||||
VS Code launched with [snippet support](/docs/customization/usersnippets.md), and we've added some notable enhancements in this release.
|
||||
VS Code launched with [snippet support](/docs/editor/userdefinedsnippets.md), and we've added some notable enhancements in this release.
|
||||
|
||||
**User-defined snippets**
|
||||
|
||||
|
|
|
|||
|
|
@ -21,22 +21,11 @@ We broke down the content into four sections:
|
|||
* [Overview](/docs) - A quick summary of all the documentation including a video overview
|
||||
* [Editor](/docs/editor/codebasics.md) - An introduction to VS Code itself from editing all the way to debugging and tasks
|
||||
* [Languages](/docs/languages/overview.md) - Walkthroughs on how to get the best out of VS Code when using specific languages e.g. JavaScript
|
||||
* [Runtimes](/docs/runtimes/nodejs.md) - Walkthroughs on how to use VS Code with specific runtimes e.g. Node.js
|
||||
|
||||
|
||||
|
||||
>**Tip:** You can search our site via the search box in the header.
|
||||
|
||||
|
||||
### Editor Settings and Configuration
|
||||
Since VS Code was released there have been a large number of questions around how to configure and customize the product. In part this was due to the fact we had not adequately listed out the available options in our documentation. To help address this we've:
|
||||
* Included the contents of the `settings.json` file in the [Customization topic](/docs/customization/overview.md)
|
||||
* Separated out [key bindings](/docs/customization/keybindings.md) into their own topic area
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Debugging
|
||||
|
||||
### node.js: Large data stucture improvments
|
||||
|
|
|
|||
|
|
@ -26,8 +26,6 @@ As this location is under your user directory, the content is persisted across V
|
|||
## Yo Code - Streamlined Customizations for VS Code
|
||||
We re-purposed the Yeoman generator we used for the VS Code Node.js sample `generator-code` and we are now using this to make creating common customizations easier.
|
||||
|
||||
>**Tip:** If you still want access to the sample, you can find out how on the [Node.js](/docs/runtimes/nodejs.md) page.
|
||||
|
||||
In this release of the generator, we have the ability to create two common customizations:
|
||||
|
||||
1. Additional color themes
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ A new setting `terminal.integrated.commandsToSkipShell` was added that contains
|
|||
|
||||
### Editor settings
|
||||
|
||||
There are several useful Editor [settings](/docs/customization/userandworkspace.md) in this release:
|
||||
There are several useful Editor [settings](/docs/getstarted/settings.md) in this release:
|
||||
|
||||
* `editor.renderLineHighlight` - Disables the current line highlight
|
||||
* `editor.fontWeight` - Customizes the editor's font weight (**normal**, **bold**).
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ The Hover widget UI was updated aligning it more with VS Code's IntelliSense exp
|
|||
|
||||
### Auto Save Menu Item
|
||||
|
||||
Auto Save is a great feature for many scenarios. In order to make this feature more discoverable, VS Code now has an **Auto Save** toggle right in the **File** menu. This will toggle the `files.autoSave` [setting](https://code.visualstudio.com/docs/customization/userandworkspace) in your global User `settings.json` configuration file.
|
||||
Auto Save is a great feature for many scenarios. In order to make this feature more discoverable, VS Code now has an **Auto Save** toggle right in the **File** menu. This will toggle the `files.autoSave` [setting](https://code.visualstudio.com/docs/getstarted/settings) in your global User `settings.json` configuration file.
|
||||
|
||||
### File Associations configuration
|
||||
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ Once you made your choice for the layout, we persist it for the current workspac
|
|||
|
||||
### Toggle Maximized Panel
|
||||
|
||||
We have introduced a global workbench command that maximizes the size of the panel (80% of the total height). If the panel is already maximized, this command will shrink the panel to its previous size. This is really handy when you have lots of output to review quickly. This command is not currently bound to any keyboard shortcut but you can add easily your own [keybinding](http://code.visualstudio.com/docs/customization/keybindings).
|
||||
We have introduced a global workbench command that maximizes the size of the panel (80% of the total height). If the panel is already maximized, this command will shrink the panel to its previous size. This is really handy when you have lots of output to review quickly. This command is not currently bound to any keyboard shortcut but you can add easily your own [keybinding](http://code.visualstudio.com/docs/getstarted/keybindings).
|
||||
|
||||
### Toggle Sidebar and Hide Status Bar now persisted in user settings
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ Below are links to the three platform-specific versions:
|
|||
* [macOS](https://go.microsoft.com/fwlink/?linkid=832143)
|
||||
* [Linux](https://go.microsoft.com/fwlink/?linkid=832144)
|
||||
|
||||
>**Note:** We also added a menu command to go to the [Introductory Videos](http://code.visualstudio.com/docs/introvideos/overview) on code.visualstudio.com (**Help** > **Introductory Videos**).
|
||||
>**Note:** We also added a menu command to go to the [Introductory Videos](http://code.visualstudio.com/docs/getstarted/introvideos) on code.visualstudio.com (**Help** > **Introductory Videos**).
|
||||
|
||||
### Format Document / Format Selection
|
||||
|
||||
|
|
|
|||
|
|
@ -577,7 +577,7 @@ The following example skips all internal modules but `events.js`:
|
|||
|
||||
### Support 'restart' option for 'launch' requests
|
||||
|
||||
For quite some time the VS Code node debugger supported a `restart` attribute on `attach` configurations. See [here](https://code.visualstudio.com/docs/editor/node-debugging#_attaching-to-nodejs) for details. With this release, we now support the `restart` attribute on `launch` configurations as well.
|
||||
For quite some time the VS Code node debugger supported a `restart` attribute on `attach` configurations. See [here](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_attaching-to-nodejs) for details. With this release, we now support the `restart` attribute on `launch` configurations as well.
|
||||
|
||||
If this feature is enabled, VS Code restarts a debug session whenever it detects the termination of Node.js. This feature can be used in combination with the `nodemon` utility which restarts Node.js whenever it detects that JavaScript source has been modified.
|
||||
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ You can now double-click on some resize borders (sashes) in the workbench to qui
|
|||
|
||||
The `workbench.action.reopenClosedEditor` command has been added which will reopen the most recent file removed from the working files list. The default key binding for this command is `kb(workbench.action.reopenClosedEditor)`.
|
||||
|
||||
>**Note:** Previously `kb(workbench.action.reopenClosedEditor)` had been bound to the **Run: Run Test Task** command. **Run: Run Test Task** is now not bound to any default key binding. You can [customize](https://code.visualstudio.com/docs/customization/keybindings#_customizing-shortcuts) the key bindings and change the behavior back to the previous one if desired.
|
||||
>**Note:** Previously `kb(workbench.action.reopenClosedEditor)` had been bound to the **Run: Run Test Task** command. **Run: Run Test Task** is now not bound to any default key binding. You can [customize](https://code.visualstudio.com/docs/getstarted/keybindings#_customizing-shortcuts) the key bindings and change the behavior back to the previous one if desired.
|
||||
|
||||
### Disable Emmet abbreviation expansion on Tab
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче