Visual Studio Code features a battle-tested code editor that has most of the industry standard features, but also has some delights. We've been using it to build VS Code and we hope you'll love it too. This topic will walk you through some of the notable features of the code editor.
Visual Studio Code是一款经过考验的编辑器,拥有大多数已成产业标准的特点,但同时也有惊喜。我们用这些构建出的VS Code,希望你也能爱上它。本主题将向你介绍VS Code的那些值得注意的特点。
Matching brackets will be highlighted as soon as the cursor is near one of them. The right bracket will always be found, regardless of embedded languages.
当光标接近一个括号时,与之配对的括号就会高亮显示。右括号总是会被发现,不管其嵌入的是何种语言。
Tip: You can jump to the matching bracket with
⇧⌘\
小技巧:你可以使用快捷键
⇧⌘\
直接跳转到匹配的括号处。(Windows or Linux:Ctrl+Shift+\
)
VS Code has support for multiple cursors. You can add secondary cursors (rendered thinner) with Alt+Click
. Each cursor operates independently based on the context it sits in. The most common way to add more cursors is with kb(editor.action.insertCursorBelow)
or kb(editor.action.insertCursorAbove)
that insert cursors below or above.
VS Code支持动态多光标。你可以使用Alt+Click
的方式添加第二光标(被渲染为较细的光标)。每个光标课根据其所在位置的上下文独立操作。最常用的多光标添加方式是使用快捷键⌥⌘↓
或⌥⌘↑
向上或下插入光标。(Window:Ctrl+Alt+Down
或Ctrl+Alt+Up
Linux:Shift+Alt+Down
或Shift+Alt+Up
)
Note: Your graphics card provider might overwrite these default shortcuts.
注意:你的显卡提供商可能会重写这些快捷按键。
kb(editor.action.addSelectionToNextFindMatch)
selects the word at the cursor, or the next occurrence of the current selection. kb(editor.action.moveSelectionToNextFindMatch)
moves the last added cursor to next occurrence of the current selection.
⌘D
选择光标处的词,或下一个选中词出现的位置。⌘K
⌘D
将添加一个光标到下一个选中词所出现的位置。
Tip: You can add more cursors also with
kb(editor.action.selectHighlights)
, which will add a selection at each occurrence of the current selected text or withkb(editor.action.changeAll)
, which will add a selection at each occurrence of the current word.小贴士:你也可以使用
⇧⌘L
在每个出现选中文本处添加一个光标,或使用⌘F2
在每个出现当前词的位置添加光标。(Window:Ctrl+Shift+L
、Ctrl+F2
Linux:Ctrl+Shift+L
、Ctrl+F2
)
Hold kbstyle(Shift)
and kbstyle(Alt)
while dragging to do column text selection:
按住Shift
或Alt
时,用鼠标拖动可以按列选择文本:
There are also default key bindings for column selection on OS X and Windows, but not on Linux. You can edit your keybindings.json
to bind them to something more familiar if you wish.
在OS X和Windows上同样有一些默认的列文本选择快捷键可以设置,很遗憾Linux没有这一功能。你可以编辑你的keybindings.json
文件来绑定快捷键到你希望的组合。
For example:
例如:
{ "key": "shift+alt+down", "command": "cursorColumnSelectDown",
"when": "editorTextFocus" },
{ "key": "shift+alt+left", "command": "cursorColumnSelectLeft",
"when": "editorTextFocus" },
{ "key": "shift+alt+pagedown", "command": "cursorColumnSelectPageDown",
"when": "editorTextFocus" },
{ "key": "shift+alt+pageup", "command": "cursorColumnSelectPageUp",
"when": "editorTextFocus" },
{ "key": "shift+alt+right", "command": "cursorColumnSelectRight",
"when": "editorTextFocus" },
{ "key": "shift+alt+up", "command": "cursorColumnSelectUp",
"when": "editorTextFocus" }
Quickly shrink or expand the current selection (applies to all languages). Trigger it with kb(editor.action.smartSelect.shrink)
and kb(editor.action.smartSelect.grow)
快速收缩或展开选择当前选中文本段(适用于所有语言),只需要按⌃⇧⌘←
或⌃⇧⌘→
即可。(在Windows或Linux上请按Shift+Alt+Left
或Shift+Alt+Right
)
Here's an example of expanding the selection with kb(editor.action.smartSelect.grow)
:
以下是一个展开选择的例子,使用按键⌃⇧⌘→
(Shift+Alt+Right
):
We'll always offer word completion, but for the rich languages, 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 (we call it affectionately 24x7 IntelliSense). You can always manually trigger it with kb(editor.action.triggerSuggest)
. Out of the box, kbstyle(.)
, kbstyle(Tab)
or kbstyle(Enter)
are accept triggers but you can also customize these key bindings.
Tip: The suggestions filtering supports CamelCase so you can type the upper case letters of a method name to limit the suggestions. For example, "wl" will quickly bring up WriteLine.
Tip: The 24x7 IntelliSense can be configured via the
editor.quickSuggestions
andeditor.suggestOnTriggerCharacters
settings.
In JavaScript, TypeScript or C#, parameter hints will pop up as you're typing a method invocation. You can navigate between different overloads with kbstyle(Up)
and kbstyle(Down)
and the best overload will be presented based on the arguments you pass in.
We offer built-in snippets across languages as well as support for Emmet abbreviations. You can expand Emmet abbreviations in HTML, Razor, CSS, Less, Sass, XML or Jade with kbstyle(Tab)
.
(See the Emmet cheat sheet for syntax examples.)
You can also define your own snippets: Open User Snippets under File > Preferences and select the language for which the snippets should appear. Find out more about this in the customization section of our docs.
If a language supports it, you can go to the definition of a symbol by pressing kb(editor.action.goToDeclaration)
.
If you press kbstyle(Ctrl)
and hover over a symbol, a preview of the declaration will appear:
Tip: You can jump to the definition with
kbstyle(Ctrl+Click)
or open the definition to the side withkbstyle(Ctrl+Alt+Click)
. If you opened a new editor window, you can go back to the previous editor withkb(workbench.action.focusLeftEditor)
.
You can navigate symbols inside a file with kb(workbench.action.gotoSymbol)
. By typing kbstyle(:)
the symbols will be grouped by category. Just press kbstyle(Up)
or kbstyle(Down)
and navigate to the place you want.
In C# and in TypeScript, you can jump to a symbol across files with kb(workbench.action.showAllSymbols)
. Just type the first letter of a type you want to navigate to, regardless of which file contains it, and press kbstyle(Enter)
.
You can fold regions of source code using the folding icons on the gutter between line numbers and line start. Move the mouse over the gutter to fold and unfold regions. The folding regions are evaluated based on the indentation of lines. A folding region starts when a line has a smaller indent than one or more following lines, and ends when there is a line with the same or smaller indent.
You can also use the following actions:
- Fold (
kb(editor.fold)
) folds the innermost uncollapsed region at the cursor - Unfold (
kb(editor.unfold)
) unfolds the collapsed region at the cursor - Fold All (
kb(editor.foldAll)
) folds all region in the editor - Unfold All (
kb(editor.unfoldAll)
) unfolds all regions in the editor - Fold Level X (
kb(editor.foldLevel2)
for level 2) folds all regions of level X, except the region at the current cursor position
If you open a folder that is a Git repository and begin making changes, VS Code will add useful annotations to the gutter and to the overview ruler.
- A red triangle indicates where lines have been deleted
- A green bar indicates new added lines
- A blue bar indicates modified lines
We think there's nothing worse than a big context switch when all you want is to quickly check something. That's why we support peeked editors. When you execute a Reference Search (via kb(editor.action.referenceSearch.trigger)
), or a Peek Definition (via kb(editor.action.previewDeclaration)
), we embed the result inline:
Tip: You can navigate between different references in the peeked editor and, if you need to, you can even make quick edits right there!
Tip: Clicking on the peeked editor filename or double-clicking in the result list will open the reference in the outer editor.
For languages that support it, the hover will show useful information, such as types of symbols, or, in the case of CSS below, the shape of the HTML that would match a certain CSS rule:
C# supports inline reference information, that is live updated. This allows you to quickly analyze the impact of your edit or the popularity of your specific method or property throughout your project:
Tip: Directly invoke the Find References action by clicking on these annotations.
Tip: Reference information can be turned on or off through the
editor.referenceInfos
setting.
TypeScript and C# support rename symbol across files. Simply press kb(editor.action.rename)
and then type the new desired name and press kbstyle(Enter)
. All usages of the symbol will be renamed, across files.
Warnings or Errors can be generated either via configured tasks or by the rich language services, that constantly analyze your code in the background. Since we love bug-free code, warnings and errors show up in multiple places:
- In the status line there is a summary of all errors and warnings counts.
- You can click on the summary or press
kb(workbench.action.showErrorsWarnings)
to see a list of all current errors. - If you open a file that has errors or warnings, they will be rendered inline with the text and in the overview ruler.
Tip: To loop through errors or warnings in the current file, you can press
kb(editor.action.marker.next)
orkb(editor.action.marker.prev)
which will show an inline zone detailing the problem and possible code actions (if available):
Now that you know how the editor works, time to try a few other things...
- Why VS Code - Why we exist and where we think we can help
- The Basics - Basic orientation around VS Code
- Debugging - This is where VS Code really shines
- Customization - Configure VS Code the way you want - Themes, Settings