Revert "test CI build without older release notes assets"
This reverts commit fcea8936fe.
This commit is contained in:
gregvanl
Родитель
8a6ba10b29
Коммит
bef0bd5537
|
|
@ -0,0 +1,210 @@
|
|||
---
|
||||
Order:
|
||||
TOCTitle: July 2016
|
||||
PageTitle: Visual Studio Code July 2016 1.4
|
||||
MetaDescription: See what is new in the Visual Studio Code July 2016 Release (1.4)
|
||||
MetaSocialImage: July_2016/social.jpg
|
||||
---
|
||||
# July 2016 (version 1.4)
|
||||
|
||||
During July, we slowed down feature work in favor of reducing our bug backlog and removing engineering debt. However, we were still able to add some improvements.
|
||||
|
||||
Here are the highlights:
|
||||
|
||||
* **Workbench**: Editor actions such as **Open Preview** and **Switch to Changes View** are back on the title bar. IME and Copy/Paste support in the Integrated Terminal.
|
||||
* **Editor**: Better snippet and suggestions control. New **Insert Snippet** command with dedicated UI.
|
||||
* **Debugging**: **Restart Frame** action to rerun a specific stack frame. 'Variable paging' feature moved into VS Code and available to all debug extensions.
|
||||
* **Extension Authoring**: New 'move' commands to better support VIM gestures. Custom link behavior with the `DocumentLinkProvider` API. Expanded Debug Protocol.
|
||||
|
||||
Downloads: [Windows](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/VSCodeSetup-stable.exe) |
|
||||
[OS X](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/VSCode-darwin-stable.zip) | Linux 64-bit: [.zip](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/VSCode-linux-x64-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/code_1.4.0-1470329130_amd64.deb) [.rpm](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/code-1.4.0-1470329130.el7.x86_64.rpm) | Linux 32-bit: [.zip](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/VSCode-linux-ia32-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/code_1.4.0-1470328389_i386.deb) [.rpm](https://az764295.vo.msecnd.net/stable/6276dcb0ae497766056b4c09ea75be1d76a8b679/code-1.4.0-1470328389.el7.i386.rpm)
|
||||
|
||||
## Editor
|
||||
|
||||
### Snippets and Suggestions
|
||||
|
||||
By default, VS Code shows snippets and completion proposals in one widget. This is not always desirable so we added a new configuration setting called `editor.snippetSuggestions`. To remove snippets from the suggestions widget, set the value to `"none"`. If you'd like to see snippets, you can specify the order relative to suggestions; at the top (`"top"`), at the bottom (`"bottom`"), or inline ordered alphabetically (`"inline"`). The default is `"inline"`.
|
||||
|
||||
In addition, we added a new command to insert a snippet, **Insert Snippet**, which displays the available snippets in a dropdown.
|
||||
|
||||
|
||||
|
||||
### Tab Completion
|
||||
|
||||
The editor now supports `kbstyle(Tab)` completions. You can enable it with the `editor.tabCompletion` setting. After typing the prefix of a snippet, press `kbstyle(Tab)` to insert it.
|
||||
|
||||
|
||||
|
||||
Note that quick suggestions and `kbstyle(Tab)` completion might interfere because the suggestions widget also reacts to `kbstyle(Tab)`.
|
||||
|
||||
Either disable quick suggestions:
|
||||
|
||||
```json
|
||||
{
|
||||
"editor.quickSuggestions": false
|
||||
}
|
||||
```
|
||||
|
||||
or remove snippets from the suggest widget:
|
||||
|
||||
```json
|
||||
{
|
||||
"editor.snippetSuggestions": "none"
|
||||
}
|
||||
```
|
||||
|
||||
## Workbench
|
||||
|
||||
### Editor Actions
|
||||
|
||||
When we added Tabs (tabbed headings), we put editor actions (**Switch to Changes View**, **Open Preview**) into the context menu to gain some space. User feedback was clear that this made the actions much harder to discover and so we have added them back to the title header.
|
||||
|
||||
|
||||
|
||||
### Drag and Drop
|
||||
|
||||
You can now drag and drop Tabs (tabbed headings) across windows. You can now also drop a folder into VS Code to open it.
|
||||
|
||||
### Git commit message template
|
||||
|
||||
If you have a message template configured in your Git settings, then the Git view in VS Code will show that message in the commit message box by default. Thanks to [William Raiford](https://github.com/bill-mybiz) for contributing this feature.
|
||||
|
||||
### Faster Quick Open
|
||||
|
||||
We made the first steps in improving the performance of **Quick Open**, particularly for large workspaces such as [Chromium](https://www.chromium.org). On Mac (`kbstyle(⌘+P)`) and on Linux (`kbstyle(Ctrl+P)`), **Quick Open** on a Chromium workspace now takes less than half the time it took before. On Windows (`kbstyle(Ctrl+P)`), it originally took twice as long as on Mac and now it is just as fast. We are not finished, expect more performance gains in the next iteration.
|
||||
|
||||
### Integrated Terminal
|
||||
|
||||
The integrated terminal had several changes related to polish and compatibility this release:
|
||||
|
||||
- **IME support**: Input Method Editor (IME) support has been implemented, allowing input of CJK and Indic characters.
|
||||
|
||||
|
||||
|
||||
- **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.
|
||||
|
||||
## Languages
|
||||
|
||||
### JSON completions
|
||||
|
||||
There has been some small improvements for the JSON completions:
|
||||
|
||||
- In schema based JSON documents, we offer completions for empty arrays, objects and string if we know the type of a property but the schema doesn't describe any defaults.
|
||||
- Completion support for the `$schema` property and values.
|
||||
|
||||
## Debugging
|
||||
|
||||
### Restart Frame
|
||||
|
||||
VS Code now supports restarting execution at a stack frame. This can be useful in situations where you have found a problem in your source code and you want to rerun a small portion of the code with modified input values. Stopping and then restarting the full debug session can be very time-consuming. The **Restart Frame** action allows you to re-enter the current function after you have changed variables with the **Set Value** action:
|
||||
|
||||
|
||||
|
||||
Note that **Restart Frame** won't unroll any state changes, so it may not always work as expected.
|
||||
|
||||
**Restart Frame** is only available if the underlying debug extension supports it and currently only VS Code's built-in Node.js debugging does. Make sure to use a Node.js version >= 5.11 since earlier versions do not work in all situations.
|
||||
|
||||
### Variable Paging
|
||||
|
||||
Previously VS Code expected that large data structures like arrays were broken into "chunks" in a debug extension and consequently only a few debug extensions supported this useful feature. With this release, we have moved this functionality into the VS Code debugger front-end so that all debug extensions can easily benefit from this in the future.
|
||||
|
||||
|
||||
|
||||
See section "Debug Protocol Changes" below for details of how a debug extension can make use of this.
|
||||
|
||||
### Double Click Debug Toolbar Centers
|
||||
|
||||
Double clicking on the Debug view toolbar drag icon will center the Debug toolbar. This makes it easy to restore the default state.
|
||||
|
||||
## Extension Authoring
|
||||
|
||||
### New settings to replace deprecated __characterPairSupport and __electricCharacterSupport.
|
||||
|
||||
The deprecated configuration settings can now both be replaced by the `autoClosingPairs` setting in the language-configuration.json file in your extension. See [#9281](https://github.com/microsoft/vscode/issues/9281) for detailed instructions.
|
||||
|
||||
### Editor Commands
|
||||
|
||||
In order to allow the [VIM extension](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim) to make good progress on their [roadmap](https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md) particularly on up-and-down motion and `kbstyle(Tab)` related commands, we added the following editor APIs:
|
||||
|
||||
- **Move cursor:** Moves the cursor to different logical positions in the editor - See [9143](https://github.com/microsoft/vscode/issues/9143).
|
||||
|
||||
```javascript
|
||||
commands.executeCommand('cursorMove', {to: 'up', by: 'wrappedLine', value: '2'})
|
||||
```
|
||||
|
||||
- **Move active editor:** Moves the active editor across groups or across Tabs within a group - See [8234](https://github.com/microsoft/vscode/issues/8234#issuecomment-234573410).
|
||||
|
||||
```javascript
|
||||
commands.executeCommand('moveActiveEditor', {to: 'left', by: 'tab', value: '3'})
|
||||
```
|
||||
|
||||
### Sorting of groups
|
||||
|
||||
Last milestone, we added support to contribute menu items to different places in the editor. This milestone we refined sorting of groups. They are now sorted in lexicographical order with the following defaults/rules.
|
||||
|
||||
The context menu of the editor has these default:
|
||||
|
||||
* `navigation` - The `navigation` group comes first in all cases.
|
||||
* `1_modification` - This group comes next and contains commands that modify your code.
|
||||
* `9_cutcopypaste` - The last default group with the basic editing commands.
|
||||
|
||||
|
||||
|
||||
You can add menu items to these groups or add new groups of menu items in between, below, or above. In this release, only the editor context menu allows this grouping control but it will soon be available for the editor title menu and the explorer context menu as well.
|
||||
|
||||
### DocumentLinkProvider API
|
||||
|
||||
VS Code has a built in link detector that finds `http`, `https`, and `file` links to make them clickable in the editor. We have added new API that allows extension writers to add custom link detection logic. Implement a `DocumentLinkProvider` and use the [`registerDocumentLinkProvider`](https://github.com/microsoft/vscode/blob/main/src/vs/vscode.d.ts#L3814) function to register it with the editor.
|
||||
|
||||
### Debug Extension Authoring: Additions to the Debug Protocol
|
||||
|
||||
The [debug protocol](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts) has been extended in the following areas (and VS Code already provides the corresponding UI):
|
||||
|
||||
* **Restart Frame**: If a debug adapter returns the capability `supportsRestartFrame`, VS Code shows a **Restart Frame** action in the context menu of the **CALL STACK** view and calls the new `restartFrame` request upon execution of the **Restart Frame** action. The `restartFrame` request must result in a `StoppedEvent` so that the UI can be updated for the new location.
|
||||
* **Variable Paging**: 'Variables paging' adds support for paging variables and their children. The debugger UI in VS Code 1.4 uses this to present variables with many children with a better scalable (paged) UI and fetches the children in a piecemeal way. A debug adapter can find out whether the client supports variable paging by checking the value of the `supportsVariablePaging` client capability passed as an argument to the `initializeRequest`.<br>
|
||||
Through the optional attributes `indexedVariables` and `namedVariables`, the debug adapter can return both the number of indexed properties (e.g. array slots) and named properties of a variable. These two properties can be returned in all places where a `variablesReference` property is returned, that is in the `Variables` and `Scope` data types and in the `evaluateRequest` response.<br>
|
||||
Additional optional attributes have been added to the `variablesRequest` to give the VS Code debugger UI better control over what children of a variable to fetch. An attribute `filter` is used to limit the fetched children to either `indexed` or `named` and the attributes `start` and `count` are used to further limit the children to a certain range.
|
||||
* **Continued Event**: A debug adapter can now optionally send a `ContinueEvent` to the client to indicate that the execution of the debuggee has continued.
|
||||
* **Source request supports MIME type**: A debug adapter can now set a `mimeType` attribute on the `SourceRequest` response which a client can use to find a suitable editor.
|
||||
* **Variable Type client capability**: A debug adapter can find out whether the client shows the variable's type attribute in the UI by checking the value of
|
||||
the `supportsVariableType` client capability passed as an argument to the `initializeRequest`.
|
||||
|
||||
## Notable Changes
|
||||
|
||||
* [4842](https://github.com/microsoft/vscode/issues/4842): Allow to disable drag and drop in the files explorer
|
||||
* [7839](https://github.com/microsoft/vscode/issues/7839): Sometimes SVG icons do not show up on Windows 7
|
||||
* [8788](https://github.com/microsoft/vscode/issues/8788): Weird tabs auto scrolling behaviour
|
||||
* [8704](https://github.com/microsoft/vscode/issues/8704): Deleting folder containing dirty files closes dirty editors
|
||||
* [8617](https://github.com/microsoft/vscode/issues/8617): Run selected text in active terminal is not running the selected text on Windows
|
||||
* [8219](https://github.com/microsoft/vscode/issues/8219): Lines containing unicode characters in integrated terminal differ in height
|
||||
* [9010](https://github.com/microsoft/vscode/issues/9010): Global search and replace: Support regular expression variables in replace
|
||||
|
||||
These are the [closed bugs](https://github.com/microsoft/vscode/issues?q=is%3Aissue+label%3Abug+milestone%3A%22July+2016%22+is%3Aclosed) and these are the [closed feature requests](https://github.com/microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22July+2016%22+is%3Aclosed+label%3Afeature-request) for the 1.4 update.
|
||||
|
||||
## Thank You
|
||||
|
||||
Last but certainly not least, a big *__Thank You!__* to the following folks that helped to make VS Code even better:
|
||||
|
||||
* [Lucian Wischik (@ljw1004)](https://github.com/ljw1004): Fix small typo [PR vscode-languageserver-node-example#17](https://github.com/microsoft/vscode-languageserver-node-example/pull/17)
|
||||
* [Markus Westerlind (@Marwes)](https://github.com/Marwes): DidOpenTextDocumentParams does not extend TextDocumentIdentifier [PR language-server-protocol#36](https://github.com/microsoft/language-server-protocol/pull/36)
|
||||
* [Eshwar Andhavarapu (@gontadu)](https://github.com/gontadu): Added more T-SQL keywords [PR #9469](https://github.com/microsoft/vscode/pull/9469)
|
||||
* [Pouya Kary (@pmkary)](https://github.com/pmkary): Added missing "rem" unit [PR #9497](https://github.com/microsoft/vscode/pull/9497)
|
||||
* [xzper (@f111fei)](https://github.com/f111fei):
|
||||
* Fix extracting zip file [PR #7599](https://github.com/microsoft/vscode/pull/7599)
|
||||
* Fix installing extension by dropping [PR #8786](https://github.com/microsoft/vscode/pull/8786)
|
||||
* Fix debounceEvent [PR #9186](https://github.com/microsoft/vscode/pull/9186)
|
||||
* [Sorin Iclanzan (@iclanzan)](https://github.com/iclanzan): Fix sensitivity not always being applied. [PR #9005](https://github.com/microsoft/vscode/pull/9005)
|
||||
* [Tamas Kiss (@kisstkondoros)](https://github.com/kisstkondoros):
|
||||
* Fixes invisible cursor in long editor lines [PR #8854](https://github.com/microsoft/vscode/pull/8854)
|
||||
* Fixes mousewheel zoom in case of inline diff view [PR #8853](https://github.com/microsoft/vscode/pull/8853)
|
||||
* New cursor animation styles implemented [PR #8153](https://github.com/microsoft/vscode/pull/8153)
|
||||
* [一丝 (@yisibl)](https://github.com/yisibl): Add Selection To Previous Find Match [PR #8677](https://github.com/microsoft/vscode/pull/8677)
|
||||
* [Giorgos Retsinas (@elemongw)](https://github.com/elemongw): [Mac] `kbstyle(Ctrl+P)` and `kbstyle(Ctrl+N)` for up and down navigation. [PR #7316](https://github.com/microsoft/vscode/pull/7316)
|
||||
* [William Raiford (@bill-mybiz)](https://github.com/bill-mybiz): Git commit message templates, restore previous message on undo. [PR #8933](https://github.com/microsoft/vscode/pull/8933)
|
||||
* [Georgios Kalpakas (@gkalpak)](https://github.com/gkalpak): docs(LanguageConfiguration): fix typo [PR #8703](https://github.com/microsoft/vscode/pull/8703)
|
||||
* [David Wilson (@daviwil)](https://github.com/daviwil):
|
||||
* Roll back PowerShell syntax definition [PR #9922](https://github.com/microsoft/vscode/pull/9923)
|
||||
* Fixes for PowershellSyntax.tmLanguage [PR #9707](https://github.com/microsoft/vscode/pull/9707)
|
||||
* [David Hollinger III (@dhollinger)](https://github.com/dhollinger): Remove .pp from Ruby extension list [PR #8637](https://github.com/microsoft/vscode/pull/8637)
|
||||
|
|
@ -0,0 +1,520 @@
|
|||
---
|
||||
Order:
|
||||
TOCTitle: June 2016
|
||||
PageTitle: Visual Studio Code June 2016 1.3
|
||||
MetaDescription: See what is new in the Visual Studio Code June 2016 Release (1.3)
|
||||
MetaSocialImage: June_2016/social.jpg
|
||||
---
|
||||
# June 2016 (version 1.3)
|
||||
|
||||
## 1.3.1 Recovery build
|
||||
|
||||
To fix several issues, we're releasing a 1.3.1 recovery build. You can view the resolved issues [here](https://github.com/microsoft/vscode/milestone/24?closed=1).
|
||||
|
||||
Downloads: [Windows](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/VSCodeSetup-stable.exe) |
|
||||
[OS X](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/VSCode-darwin-stable.zip) | Linux 64-bit [.zip](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/VSCode-linux-x64-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/code_1.3.1-1468329898_amd64.deb) [.rpm](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/code-1.3.1-1468329898.el7.x86_64.rpm) | Linux 32-bit [.zip](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/VSCode-linux-ia32-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/code_1.3.1-1468330706_i386.deb) [.rpm](https://az764295.vo.msecnd.net/stable/e6b4afa53e9c0f54edef1673de9001e9f0f547ae/code-1.3.1-1468330706.el7.i386.rpm)
|
||||
|
||||
## June Release Summary
|
||||
|
||||
We're really excited about the June release of VS Code. We've made some big changes to Extension management (dedicated Extensions View) and added Tabs (tabbed editor panes). Other new features include global Search and Replace, improved Drag and Drop and optional indentation guides. All of this along with enhancements to existing features like the Integrated Terminal and delivering a set of important bug fixes.
|
||||
|
||||
Here are the highlights:
|
||||
|
||||
* **Tabs**: Tabbed editor panes allow you to quickly navigate to your files and organize your workbench.
|
||||
* **Extensions**: New in-product Extensions View to quickly find, install and manage your extensions.
|
||||
* **Workbench**: Enhanced Drag and Drop, Preview Editors to conserve your editor panes, and multiple Integrated Terminals.
|
||||
* **Editor**: Global Search and Replace, Indent Guides, Problems panel to view errors and warnings.
|
||||
* **Languages**: Better, more complete Emmet support, Atom JavaScript grammar extension.
|
||||
* **Debugging**: Lots of improvements including support for attaching to running Node.js processes and changing variable values during a debug session.
|
||||
* **Extension Authoring**: A new contribution point for menu bars and context menus. New APIs to open non-text resources and add editor decorator attachments.
|
||||
|
||||
## Tabs
|
||||
|
||||
With this release, VS Code shows open files as Tabs in the title area above the editor. You can move Tabs around via Drag and Drop to organize your files or right-click on a Tab to perform useful file specific actions.
|
||||
|
||||
|
||||
|
||||
If you prefer not to use Tabs, you can disable them through the `workbench.editor.showTabs` setting.
|
||||
|
||||
When there is not enough available space to show all files, you will see Tabs overflowing to the left and right. You can always use the mouse to scroll left and right across all tabs. The little overflow icon (see image below) is enabled as soon as there are Tabs outside of the visible view. Clicking on the overflow icon shows a list of all Tabs opened in the group.
|
||||
|
||||
|
||||
|
||||
You can use the new `workbench.editor.openPositioning` setting to control where new editors should open. By default they open to the right of the active Tab, but you can change this to open to the left, or to the beginning or end of all editors.
|
||||
|
||||
### Open Editors View
|
||||
|
||||
The new **OPEN EDITORS** view in the Explorer is the replacement to the previous **WORKING FILES** view.
|
||||
|
||||
|
||||
|
||||
The **OPEN EDITORS** view is a visual representation of the editor (open file) stacks:
|
||||
|
||||
* Each editor group with the editors that belong to it is shown.
|
||||
* Clicking on an editor will make it active and open it in the corresponding group.
|
||||
* Top level actions to close all or save all open editors.
|
||||
* Editor level actions to close or save an editor.
|
||||
* Context menu actions provide more refined actions.
|
||||
* It is possible to drag and drop editors between editor groups or from the Explorer
|
||||
|
||||
You can hide the **OPEN EDITORS** view by setting the number of visible items to 0, with `"explorer.openEditors.visible": 0`.
|
||||
|
||||
**Note:** Since the WORKING FILES view has been deleted, please refer to [this issue](https://github.com/microsoft/vscode/issues/6605) to get an overview of the new or changed command identifiers.
|
||||
|
||||
### More on Editor Stacks
|
||||
|
||||
As a preparation for enabling Tabs in the workbench, we revisited how you can interact with editors in VS Code. Many users coming from other tools were confused by some of the editor (open file) behavior in VS Code.
|
||||
|
||||
For example:
|
||||
|
||||
* Closing a dirty editor (an editor with an unsaved file) did not prompt for saving.
|
||||
* Closing an editor, closed the entire group without revealing the previous editor.
|
||||
* The editor history showed a list of all editors ever opened and not a list of editors you opened in a group.
|
||||
* **WORKING FILES** view in the Explorer was a confusing concept.
|
||||
|
||||
With editor **stacks**, we've tried to address these issues:
|
||||
|
||||
* You can open up to 3 **editor groups** side by side and each group contains a **stack of editors**.
|
||||
* Every time you open an editor, it is added to the top of the stack.
|
||||
* Closing an editor from a group reveals the editor that was previously opened in that group until the last editor closes and the group hides.
|
||||
* You get prompted to save for dirty editors.
|
||||
|
||||
Use `kb(workbench.action.quickOpenPreviousRecentlyUsedEditorInGroup)` to bring up a list of most recently used editors of a group for navigation. Use the **View: Show All Editors** command to show a list of all open editors across all groups.
|
||||
|
||||
|
||||
|
||||
Note that the behavior of editor stacks is independent from having Tabs enabled or not. You will benefit from these changes even if you don't want to use Tabs.
|
||||
|
||||
**Note:** Due to the large conceptual impact of editor stacks, many command ids have been renamed and new commands introduced. Please refer to [this issue](https://github.com/microsoft/vscode/issues/6605) that documents the changes. It also provides guidance if you liked the previous behavior and explains how to change key bindings back to the old behavior.
|
||||
|
||||
## Extension Management
|
||||
|
||||
We have introduced a new Extensions View to improve finding, installing, and updating VS Code [extensions](/docs/editor/extension-marketplace.md).
|
||||
|
||||
To display the Extensions View, click the Extensions View icon or press `kb(workbench.view.extensions)`:
|
||||
|
||||
|
||||
|
||||
By clicking on the `...` **More Actions** button, it is possible to show:
|
||||
|
||||
* The list of currently installed extensions
|
||||
* The list of outdated extensions that can be updated
|
||||
* The list of recommended extensions based on your workspace
|
||||
* The list of globally popular extensions
|
||||
|
||||
Clearing the search box, shows the list of installed extensions.
|
||||
|
||||
Browsing through a list of extensions, it is possible to install, uninstall or update them. Clicking on an extension will display the detailed description in the editor area.
|
||||
|
||||
|
||||
|
||||
## Workbench
|
||||
|
||||
### Errors and Warning in the Problems panel
|
||||
|
||||
With the June release, we now offer a new **Problems** panel, docked at the bottom of VS Code, that shows errors, warnings and other information generated by different sources like language servers, linters and others. In previous releases, we showed the errors and warnings in the quick box at the top of the editor. We have received feedback from users that this made it difficult to review errors and warnings while editing files. The new panel makes it easy to navigate through your errors and warnings and fix them while the editor is still open.
|
||||
|
||||
|
||||
|
||||
A filter box is provided to search and filter among the problems shown. You can either filter by type or by text. For example, 'errors' will filter for all problems of type error. 'character' will filter for problems with messages containing the word 'character'.
|
||||
|
||||
You can open the **Problems** panel by:
|
||||
|
||||
* Using `kb(workbench.actions.view.problems)`
|
||||
* From the **View** | **Problems** menu
|
||||
* From the **View** > **Show Problems** command in the **Command Palette**
|
||||
|
||||
The key binding `kb(workbench.actions.view.problems)` that was used to show errors and warnings in the quick open/quick box will now open the **Problems** panel.
|
||||
|
||||
By default, the **Problems** panel scrolls and shows problems for your active file. If you don't want this automatic reveal behavior, you can disable it through a setting `problems.autoReveal`. Set `problems.autoReveal` to `false` to prevent your Problems view from changing as you switch between active files.
|
||||
|
||||
>**Note:** This view is just a representation of markers generated by the language servers or linters or build tasks or any external builders configured in or outside your workspace. You have to configure or customize them appropriately in order to see the expected problems.
|
||||
|
||||
### More powerful Drag and Drop
|
||||
|
||||
With all the work on Tabs, we also looked at improving the Drag & Drop support in the editor. We always allowed you to drop files from outside VS Code into the editor to open the files and now there is a lot more that you can do:
|
||||
|
||||
#### Drop to Split
|
||||
|
||||
Drag some files to the left or right area of an editor to open it to the side of that editor. You can either drag from the Explorer or a Tab if Tabs are enabled.
|
||||
|
||||
|
||||
|
||||
#### Drop Feedback
|
||||
|
||||
Whenever you are dragging files or a Tab over the editor area, you now get drop feedback to indicate the target position of the drop.
|
||||
|
||||
#### Drag from Explorer and Opened Editors view
|
||||
|
||||
You can now drag a file or editor from the Explorer and the **OPEN EDITORS** view to the editor space to open it at a specific location.
|
||||
|
||||
### Preview Editors
|
||||
|
||||
Closely related to editor stacks and Tabs are **preview editors**. If you are browsing many files, you might not want to see a Tab opened for each file you open. Preview editors help reduce the number of opened editors (and Tabs) by reusing the current editor. A file will open in preview mode if you open it by single clicking in the Explorer. As long as the editor stays in preview mode, other files will open in the same location as the preview editor.
|
||||
|
||||
Certain actions cause a preview editor to become a normal editor:
|
||||
|
||||
* When you modify the contents of a file, the editor will be kept open.
|
||||
* The same is true for when you double-click on a file in the Explorer or inside a Tab or move a file to a specific editor group.
|
||||
|
||||
Preview editors are indicated using an italic font style.
|
||||
|
||||
|
||||
|
||||
We introduced new settings to control the behavior of preview editors:
|
||||
|
||||
* `workbench.editor.enablePreview` to globally enable or disable preview editors.
|
||||
* `workbench.editor.enablePreviewFromQuickOpen` to enable or disable preview editors when opened from quick box/quick open.
|
||||
|
||||
### Integrated Terminal
|
||||
|
||||
The integrated terminal that was introduced in VS Code 1.2.0 has seen many improvements this release, the primary one being the ability to launch and use multiple terminals at the same time. Terminal instances can be added by hitting the plus icon on the top-right of the **TERMINAL** panel or by triggering the `kb(workbench.action.terminal.new)` command. This creates another entry in the dropdown list that can be used to switch between them.
|
||||
|
||||
|
||||
|
||||
Several new commands were added to aid with management of the **TERMINAL** panel and its terminal instances.
|
||||
|
||||
They are:
|
||||
|
||||
* `workbench.action.terminal.focus`: Focus the terminal. This is like toggle but focuses the terminal instead of hides it, if it is visible.
|
||||
* `workbench.action.terminal.focusNext`: Focuses the next terminal instance.
|
||||
* `workbench.action.terminal.focusPrevious`: Focuses the previous terminal instance.
|
||||
* `workbench.action.terminal.kill`: Remove the current terminal instance.
|
||||
|
||||
The ability to run selected text in the current terminal has been added through the `workbench.action.terminal.runSelectedText` command.
|
||||
|
||||
To use this command, select text in an editor and run the command via the **Command Palette**:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The following improvements were also added:
|
||||
|
||||
* Copy and paste on Linux and Windows is now available using `kbstyle(Ctrl+Insert)` and `kbstyle(Shift+Insert)` respectively. This is temporarily non-configurable until we can [route custom copy/paste keybindings](https://github.com/sourcelair/xterm.js/issues/118) to the xterm.js library.
|
||||
* CJK characters should now use the correct width. Credit for this goes to [@jerch](https://github.com/jerch) in [this PR](https://github.com/sourcelair/xterm.js/pull/144).
|
||||
* Performance of the terminal has improved significantly and should no longer perform poorly when running commands that produce large output.
|
||||
* `kbstyle(Ctrl+Left)` and `kbstyle(Ctrl+Right)` now tells the underlying shell to jump over words in the input.
|
||||
* Terminal cursor blinking is now enabled by default. It shares the configuration value with the editor's `editor.cursorBlinking` setting.
|
||||
* A hollow cursor is shown when the terminal is not focused.
|
||||
* Terminal font size and line height can be customized via settings, thanks to a [PR](https://github.com/microsoft/vscode/pull/6998) from [@kisstkondoros](https://github.com/kisstkondoros).
|
||||
* Selection has been improved to now select the full line, contain no margin and also invert the text colors.
|
||||
|
||||
* Arguments can be passed to the terminal shell on Linux and OS X using the `terminal.integrated.shellArgs.*` settings.
|
||||
|
||||
### Command Palette: File: Open Recent in new Window
|
||||
|
||||
The command **File: Open Recent** from the **Command Palette** makes it very easy to quickly switch between previously opened folders or files. Usually the selected file or folder would open in the running instance. In this release, we added support to open into a new window if you select an entry while having the `kbstyle(Ctrl)` (`kbstyle('Cmd')` on Mac) key pressed.
|
||||
|
||||
### Restore Full screen
|
||||
|
||||
A new setting `window.restoreFullscreen` has been added to open VS Code in full screen if it was previously closed in full screen mode.
|
||||
|
||||
## Editor
|
||||
|
||||
### Global Search and Replace
|
||||
|
||||
[Global Search and Replace](https://github.com/microsoft/vscode/issues/1690) was one of the most requested features from our users. With this release, we enhanced our Search view to include Replace functionality so that you can replace text across multiple files. You can replace in all files or pick file by file or result by result. You can also exclude results or files and then perform replace on the rest. The Search view gives you a nice preview and clicking on a pending change will bring up the Diff editor view showing the file before and after replace.
|
||||
|
||||
|
||||
|
||||
Replace functionality can be accessed:
|
||||
|
||||
* In the **Search View** by expanding the Search textbox
|
||||
* Using `kb(workbench.action.replaceInFiles)`, from the **Edit** | **Replace in Files** menu
|
||||
* Using **Replace in Files** command in the **Command Palette**
|
||||
|
||||
>**Note:** Since Search has a limitation of showing a maximum of 2048 results, Replace currently has the same limitation.
|
||||
|
||||
### Indent Guides
|
||||
|
||||
VS Code can now show indent guides, enabled with the `editor.renderIndentGuides` setting.
|
||||
|
||||
|
||||
|
||||
### Suggestions for command identifiers
|
||||
|
||||
When authoring the `keybindings.json` file, you now get completions for the available commands.
|
||||
|
||||
|
||||
|
||||
### Editor Font Zooming with mouse wheel
|
||||
|
||||
Thanks to [@kisstkondoros](https://github.com/kisstkondoros), with [PR #6990](https://github.com/microsoft/vscode/pull/6990), after setting `editor.mouseWheelZoom: true`, it is possible to change the font size of the editors by pressing `kbstyle(Ctrl)` (`kbstyle('Cmd')` on Mac) and scrolling with the mouse wheel:
|
||||
|
||||
|
||||
|
||||
### Multiline Find
|
||||
|
||||
We have added support for multiline Find and Replace:
|
||||
|
||||
|
||||
|
||||
### Emmet
|
||||
|
||||
Thanks to some great support from Denis Malinochkin ([@mrmlnc](https://github.com/mrmlnc)) through Pull Requests and testing help, we are now covering many more Emmet features (Wrap with Abbreviation, Remove Tag, Update Tag, Balance, Toggle Comment, ...).
|
||||
|
||||
## Languages
|
||||
|
||||
### Extract CSS/LESS/SCSS and JSON into extensions
|
||||
|
||||
The CSS, LESS, and SCSS language support has been refactored to be regular VS Code extensions. As all these languages are based on the same code base, they share the same language server. The language server runs in a separate node process, using the [language server protocol](https://microsoft.github.io/language-server-protocol) to communicate with VS Code.
|
||||
|
||||
### Extract Markdown into an extension
|
||||
|
||||
The Markdown language support has been refactored to be a regular VS Code extension. It uses the Markdown TextMate grammar for syntax highlighting source and renders the Markdown as HTML using the [markdown-it library](https://github.com/markdown-it/markdown-it) which implements the [CommonMark Spec](https://spec.commonmark.org/0.25/).
|
||||
|
||||
### Atom JavaScript grammar
|
||||
|
||||
As an alternative to the built-in JavaScript grammar, you can now install the [Atom JavaScript grammar](https://marketplace.visualstudio.com/items?itemName=ms-vscode.js-atom-grammar). It differs from the built-in grammar in that it creates tokens for variable and function references which, if supported by the theme, can be colorized differently.
|
||||
|
||||
## Debugging
|
||||
|
||||
### Moveable Debug Toolbar
|
||||
|
||||
Initiated by this [user request](https://github.com/microsoft/vscode/issues/4580), it is now possible to drag the debug toolbar horizontally:
|
||||
|
||||
|
||||
|
||||
### Changing Variable Value
|
||||
|
||||
We now support changing the value of simple variables if a debug extension supports this.
|
||||
|
||||
Node Debug is the first extension to do so:
|
||||
|
||||
|
||||
|
||||
A simple variable is a leaf in the variables tree, e.g. a variable, an object property, or an array element.
|
||||
|
||||
### Show Variable Type on Hover
|
||||
|
||||
If a debug extension supports variable types, we now show the type when hovering over the variable name.
|
||||
|
||||
### Step Back
|
||||
|
||||
If a debug extension supports _step back_ we now expose a step back action and button:
|
||||
|
||||
|
||||
|
||||
### OS specific launch configurations
|
||||
|
||||
Initiated by a [user request](https://github.com/microsoft/vscode/issues/1873), it is now possible to specify OS specific configurations inside a `launch.json`:
|
||||
|
||||
```json
|
||||
{
|
||||
"type": "node",
|
||||
"request": "launch",
|
||||
"runtimeExecutable": "mynode",
|
||||
"windows": {
|
||||
"runtimeExecutable": "mynode.exe"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Node.js Debugging
|
||||
|
||||
### Attach to Process
|
||||
|
||||
Node.js debugging now supports attaching to a Node.js process that has not been started in debug mode. This can be useful if you need to debug a production server that cannot always run in debug mode for performance reasons.
|
||||
|
||||
In order to attach to a Node.js process, you specify its _process id_ via a `processId` attribute in an `attach` launch configuration.
|
||||
|
||||
Since it is not very practical to always having to edit the launch configuration before starting a debug session, we've introduced a new type of variable that can bind to an interactive UI, e.g. to a process picker:
|
||||
|
||||
|
||||
|
||||
Here is a launch configuration that uses the `${command:PickProcess}` variable to let the user select a Node.js process before starting the debug session:
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Attach to Process",
|
||||
"type": "node",
|
||||
"request": "attach",
|
||||
"processId": "${command:PickProcess}"
|
||||
}
|
||||
```
|
||||
|
||||
## Extension Authoring
|
||||
|
||||
### Menu Items and Context Menu Entries
|
||||
|
||||
We now allow extension writers to contribute to the Explorer context menu (`explorer/context`), the editor context menus (`editor/context`), and the editor title menu (`editor/title`).
|
||||
|
||||
It works in two steps:
|
||||
|
||||
1. Assign a title and an icon to a command using the enhanced `commands` contribution point.
|
||||
2. Create menu items using the new `menus` contribution point.
|
||||
|
||||
A menu item is defined for a menu location like `editor/context` and must at least specify the `command` to run. To avoid overly cluttered menus, a menu item should also specify a condition under which it shows. Last, an alternative command and a group into which the item is sorted can be defined. Groups are visually separated and there is a special group called _navigation_ which is the most prominent.
|
||||
|
||||
```json
|
||||
{
|
||||
"commands": [
|
||||
{
|
||||
"command": "markdown.showPreview",
|
||||
"title": "Open Preview",
|
||||
"icon": {
|
||||
"light": "./media/Preview.svg",
|
||||
"dark": "./media/Preview_inverse.svg"
|
||||
}
|
||||
}
|
||||
],
|
||||
"menus": {
|
||||
"explorer/context": [
|
||||
{
|
||||
"when": "resourceLangId == markdown",
|
||||
"command": "markdown.showPreview",
|
||||
"group": "navigation"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
The snippet above adds an entry into the navigation group of the Explorer context menu **when** the resource is of the Markdown language. *Note* that the URI of the current resource is passed to the command when being executed from a menu item.
|
||||
|
||||
### Add decorations before and after text
|
||||
|
||||
New capabilities have been added to the decoration APIs. You can now add 'attachments' before and after a decoration. Attachments can be icons as well as text content that sticks to the decorated text.
|
||||
|
||||
An example are the CSS color decorators attached to color values in the text:
|
||||
|
||||
|
||||
|
||||
Decoration attachments can be defined on decoration types (see the `before` and `after` properties on `ThemableDecorationInstanceRenderOptions`) and fine-tuned on individual decorations (see the `before` and `after` properties on `ThemableDecorationRenderOptions`). You can review these properties in the `vscode` namespace API [reference](/docs/extensionAPI/vscode-api.md).
|
||||
|
||||
### API tweaks
|
||||
|
||||
* The Uri-class now allows you derive a Uri from an existing one: `someUri.with({scheme: 'newScheme', path: 'newPath'})`
|
||||
* The `previewHtml` command now allows you to provide a `title`.
|
||||
* When previewing html, we expose the style of the current theme via class names of the body element. Those are `vscode-light`, `vscode-dark`, and `vscode-high-contrast`.
|
||||
* Last, there is a new command `vscode.open` to open non-textual resources like images.
|
||||
|
||||
### Debug Extension Authoring: Command Variables
|
||||
|
||||
VS Code has supported variable substitution in `launch.json` configurations for some time. This release introduces a new type of variable that is bound to a VS Code _command_. When a debug session is started, all command variables that occur in the underlying launch configuration are first collected and then executed. Multiple occurrences of a variable do not result in multiple execution. Before the launch configuration is passed to the debug adapter, all variables are substituted with the command results.
|
||||
|
||||
A command is implemented and registered in an extension and its return value is used as the variable's value. The implementation of a command can range from a simple expression with no UI, to some sophisticated functionality based on the UI features available in the extension API.
|
||||
|
||||
An example for this functionality can be found in `node-debug`. Here a variable `${command:PickProcess}` is bound to a process picker command. A new 'Attach to Process' launch configuration uses the variable to let the user pick a Node.js process when running the launch configuration.
|
||||
|
||||
Introducing a new command variable is simple:
|
||||
|
||||
* Implement and register the command in your extension (not in the debug adapter).
|
||||
* Add a `variables` section to your `debuggers` contribution point.
|
||||
* Add one name/command-binding per variable.
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
"debuggers": {
|
||||
...
|
||||
"variables": {
|
||||
"RemoteHost": "askUserForRemoteHostCommand"
|
||||
},
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
* The variable can now be used in any string typed value of a launch configuration as `${command:RemoteHost}`.
|
||||
* To make the `RemoteHost` variable discoverable for the user consider adding it to the `configurationAttributes` or `initialConfigurations` sections of the `debuggers` contribution point.
|
||||
|
||||
### Debug Extension Authoring: Additions to the Debug Protocol
|
||||
|
||||
The debug protocol has been extended in three areas (and VS Code already provides the corresponding UI):
|
||||
|
||||
* **Editing variables**: If a debug adapter returns the [capability `supportsSetVariable`](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L594), VS Code supports setting the value of unstructured (leaf) variables in the Variables view by calling the [`setVariable` request](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L476).
|
||||
* **Stepping backward**: If a debug adapter returns the [capability `supportsStepBack`](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L592), VS Code enables the UI for stepping back and will call the [`stepBack` request](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L476).
|
||||
* **Show variable type on hover**: If a debug adapter returns the optional `type` attribute for the [`variable` type](https://github.com/microsoft/vscode-debugadapter-node/blob/main/protocol/src/debugProtocol.ts#L741), VS Code will show the value of this attribute when hovering over the variable's name.
|
||||
|
||||
### Creating Errors/Warnings from an Extension (Diagnostics)
|
||||
|
||||
With the introduction of the new **Problems** panel, we started to work on support for project wide builders and linters. As a first step, we eliminated the automatic clearing of problems when an document is closed. Otherwise opening and closing a document would change the problem set generated by a project wide builder. Due to this change, extensions like linters generating diagnostics are responsible for clearing them when a document is closed. All extension providers generating diagnostics need to adopt to this change.
|
||||
|
||||
In a linter that uses the `vscode-language-server` node module, this can be achieved as follows:
|
||||
|
||||
```typescript
|
||||
documents.onDidClose((event) => {
|
||||
connection.sendDiagnostics({ uri: event.document.uri, diagnostics: [] });
|
||||
});
|
||||
```
|
||||
|
||||
## Monaco Editor
|
||||
|
||||
The Monaco Editor is now on [npm](https://www.npmjs.com/package/monaco-editor-core)! It is the VS Code source code editor extracted and packaged as a library that can be integrated in any web application to work in any modern browser. We have created a [playground](https://microsoft.github.io/monaco-editor/index.html) showcasing some of the APIs. You can get it via `npm install monaco-editor`.
|
||||
|
||||
All further Monaco Editor specific release notes will be available at its distribution [repository](https://github.com/microsoft/monaco-editor/blob/main/CHANGELOG.md).
|
||||
|
||||
|
||||
|
||||
### CSS/LESS/SCSS and JSON language services are now available
|
||||
|
||||
Additionally, the CSS/LESS/SASS parser and language intelligence source code has been extracted to a separate node module [vscode-css-languageservice](https://github.com/microsoft/vscode-css-languageservice) which is used by both the [Monaco editor](https://github.com/microsoft/monaco-editor) as well as VS Code, bringing the same CSS editing experience to the web browser.
|
||||
|
||||
Same for JSON, where the language service, including the JSON schema validator, were extracted to [vscode-json-languageservice](https://github.com/microsoft/vscode-json-languageservice) which again is shared with the [Monaco editor](https://github.com/microsoft/monaco-editor).
|
||||
|
||||
## Notable Bug Fixes
|
||||
|
||||
The SASS mode language ID has been renamed from 'sass' to 'scss'. If you have customized any linter settings for Sass, just rename the configuration keys from 'sass.' to 'scss.'.
|
||||
|
||||
* [6316](https://github.com/microsoft/vscode/issues/6316): Update should reopen all last opened folders
|
||||
* [1210](https://github.com/microsoft/vscode/issues/1210): Open file dialog should start in the directory for the current active file
|
||||
* [7391](https://github.com/microsoft/vscode/issues/7391): editor becomes unresponsive all the time since last update
|
||||
* This fix improves the memory footprint of all colorizers through the use of immutable linked lists for representing colorizer states in-between lines in [vscode-textmate](https://github.com/microsoft/vscode-textmate).
|
||||
* [8173](https://github.com/microsoft/vscode/issues/8173): Noticeable delay opening a Markdown file (source)
|
||||
* The implementation of a 10x faster hand-written plist parser for TextMate grammars improves the start-up time of all colorizers. We are looking into extracting this implementation to its own node module.
|
||||
|
||||
In addition, the following bugs were fixed with the Integrated Terminal:
|
||||
|
||||
* [#7911](https://github.com/microsoft/vscode/issues/7911): Terminal lines appears to have margin
|
||||
* [#7684](https://github.com/microsoft/vscode/issues/7684): Clicking into editor does not properly take focus from Terminal view
|
||||
* [#7458](https://github.com/microsoft/vscode/issues/7458): Runaway terminalProcess processes
|
||||
* [#6738](https://github.com/microsoft/vscode/issues/6738), [#7442](https://github.com/microsoft/vscode/issues/7442), [#7444](https://github.com/microsoft/vscode/issues/7444): Several issues related to resizing the terminal
|
||||
* [#6743](https://github.com/microsoft/vscode/issues/6743): Mouse wheel scrolling in integrated terminal only works on filled areas
|
||||
* [#7357](https://github.com/microsoft/vscode/issues/7357): Invoking the terminal sometimes yields an error "Cannot set property 'innerHTML' of undefined"
|
||||
* [#6457](https://github.com/microsoft/vscode/issues/6457): vim overrides the terminal color scheme
|
||||
|
||||
These are the [closed bugs](https://github.com/microsoft/vscode/issues?q=is%3Aissue+label%3Abug+milestone%3A%22June+2016%22+is%3Aclosed) and these are the [closed feature requests](https://github.com/microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22June+2016%22+is%3Aclosed+label%3Afeature-request) for the 1.3 update.
|
||||
|
||||
## Downloads
|
||||
|
||||
Downloads: [Windows](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/VSCodeSetup-stable.exe) |
|
||||
[OS X](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/VSCode-darwin-stable.zip) | Linux 64-bit [.zip](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/VSCode-linux-x64-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/code_1.3.0-1467909982_amd64.deb) [.rpm](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/code-1.3.0-1467909982.el7.x86_64.rpm) | Linux 32-bit [.zip](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/VSCode-linux-ia32-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/code_1.3.0-1467910772_i386.deb) [.rpm](https://az764295.vo.msecnd.net/stable/e724f269ded347b49fcf1657fc576399354e6703/code-1.3.0-1467910772.el7.i386.rpm)
|
||||
|
||||
## Thank You
|
||||
|
||||
Last but certainly not least, a big *__Thank You!__* to the following folks that helped to make VS Code even better:
|
||||
|
||||
* [Denis Malinochkin (@mrmlnc)](https://github.com/mrmlnc): Emmet - support all the features [PR #7926](https://github.com/microsoft/vscode/pull/7926), [PR #8155](https://github.com/microsoft/vscode/pull/8155), [PR #8489](https://github.com/microsoft/vscode/pull/8489)
|
||||
* [Rob Lourens (roblourens)](https://github.com/roblourens): UI support for TimeTravel Debugging [PR #7734](https://github.com/microsoft/vscode/pull/7734)
|
||||
* [xzper (f111fei)](https://github.com/f111fei): Debug: Fix setConfiguration error when name is null or undefined [PR #7636](https://github.com/microsoft/vscode/pull/7636)
|
||||
* [Thomas Stringer (tstringer)](https://github.com/tstringer): Added remove and disable all breakpoints actions [PR #7627](https://github.com/microsoft/vscode/pull/7627)
|
||||
* [Ed Munoz (edumunoz)](https://github.com/edumunoz):
|
||||
* Remove leaked breakpoint after stopping with run-to-cursor [PR #7367](https://github.com/microsoft/vscode/pull/7367)
|
||||
* report RunToCursorAction as not supported when session not stopped [PR #7371](https://github.com/microsoft/vscode/pull/7371)
|
||||
* [Giorgos Retsinas (@elemongw)](https://github.com/elemongw): Open window on activate when all windows are closed [PR #7547](https://github.com/microsoft/vscode/pull/7547)
|
||||
* [Andrew Arnott (@AArnott)](https://github.com/AArnott): LS Protocol-Clarifications regarding JSON-RPC header [PR #15](https://github.com/microsoft/language-server-protocol/pull/15)
|
||||
* [Vaclav Pavlin (@vpavlin)](https://github.com/vpavlin): LS Protocol-Fix typos in protocol.md [PR #20](https://github.com/microsoft/language-server-protocol/pull/20)
|
||||
* [Tamas Kiss (@kisstkondoros)](https://github.com/kisstkondoros):
|
||||
* Gutter icon background size limited [PR #6553](https://github.com/microsoft/vscode/pull/6553)
|
||||
* Horizontal selection movement implemented [PR #6887](https://github.com/microsoft/vscode/pull/6887)
|
||||
* Option to hide the status bar implement [PR #6942](https://github.com/microsoft/vscode/pull/6942)
|
||||
* Allow zooming with ctrl+mousewheel combination [PR #6990](https://github.com/microsoft/vscode/pull/6990)
|
||||
* Add an option to display control characters [PR #7578](https://github.com/microsoft/vscode/pull/7578)
|
||||
* fix for "screen cheese with long error messages" [PR #8432](https://github.com/microsoft/vscode/pull/8432)
|
||||
* [Basarat Ali Syed (@basarat)](https://github.com/basarat): fix : Standalone Monaco text edit validation [PR #7864](https://github.com/microsoft/vscode/pull/7864)
|
||||
* [Christian Svensson (@csvn)](https://github.com/csvn): Added order to snippet tab stops [PR #7925](https://github.com/microsoft/vscode/pull/7925)
|
||||
* [Phill (@ph1ll)](https://github.com/ph1ll): fix 'shaddow' typo [PR #7981](https://github.com/microsoft/vscode/pull/7981)
|
||||
* [Huachao Mao (@Huachao)](https://github.com/Huachao): Add Productivity into extension categories [PR #7304](https://github.com/microsoft/vscode/pull/7304)
|
||||
* [Sajjad Hashemian (@sijad)](https://github.com/sijad):
|
||||
* Improve 'Open in Terminal' on OS X. [PR #6136](https://github.com/microsoft/vscode/pull/6136)
|
||||
* Show warning for a long commit message [PR #7399](https://github.com/microsoft/vscode/pull/7399)
|
||||
* [Eshwar Andhavarapu (@gontadu)](https://github.com/gontadu):
|
||||
* Addition of USE EXEC OPENQUERY syntax [PR #8046](https://github.com/microsoft/vscode/pull/8046)
|
||||
* Added .dsql and .psql filetypes [PR #7491](https://github.com/microsoft/vscode/pull/7491)
|
||||
* [Cătălin Mariș (@alrra)](https://github.com/alrra): Treat `.webmanifest` files as JSON [PR #8019](https://github.com/microsoft/vscode/pull/8019)
|
||||
* [Øyvind Kallstad (@gravejester)](https://github.com/gravejester): Refactored PowerShell language definitions [PR #7522](https://github.com/microsoft/vscode/pull/7522)
|
||||
* [Jan Niklas Hasse (@jhasse)](https://github.com/jhasse): Highlight .mk files as a Makefile [PR #7328](https://github.com/microsoft/vscode/pull/7328)
|
||||
* [Christian Heilmann (@codepo8)](https://github.com/codepo8): Adding autocomplete values of to input/select/textarea [PR #7152](https://github.com/microsoft/vscode/pull/7152)
|
||||
|
|
@ -0,0 +1,285 @@
|
|||
---
|
||||
Order:
|
||||
TOCTitle: May 2016
|
||||
PageTitle: Visual Studio Code May 2016 1.2
|
||||
MetaDescription: See what is new in the Visual Studio Code May 2016 Release (1.2)
|
||||
---
|
||||
# May 2016 (version 1.2)
|
||||
|
||||
## 1.2.1 Recovery build
|
||||
|
||||
To fix several performance and Git integration issues, we're releasing a 1.2.1 recovery build. You can view the resolved issues [here](https://github.com/microsoft/vscode/issues?q=milestone%3A%22June+13th+Stable+Recovery%22+is%3Aclosed).
|
||||
|
||||
Downloads: [Windows](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/VSCodeSetup-stable.exe) |
|
||||
[OS X](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/VSCode-darwin-stable.zip) | Linux 64-bit [.zip](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/VSCode-linux-x64-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/vscode-amd64.deb) [.rpm](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/vscode-x86_64.rpm) | Linux 32-bit [.zip](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/VSCode-linux-ia32-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/vscode-i386.deb) [.rpm](https://az764295.vo.msecnd.net/stable/fe7f407b95b7f78405846188259504b34ef72761/vscode-i386.rpm)
|
||||
|
||||
## 1.2.0 May release
|
||||
|
||||
The May release of VS Code has some great new features, enhancements to existing features, and a set of important bug fixes.
|
||||
|
||||
Here are the highlights:
|
||||
|
||||
* [**Editor**](#editor): Ability to trim automatically inserted whitespace, a new key binding to select all find matches, and the Peek view is now resizable.
|
||||
* [**Linting**](#linters): ESLint now supports the ability to fix all problems and TSLint supports quick fixes and file exclusion.
|
||||
* [**Languages**](#languages): Code completion (IntelliSense), Go To and Peek Definition, and Find All Occurrences support for CSS variables in CSS, SCSS, and LESS files.
|
||||
* [**Workbench**](#workbench): A new integrated Terminal allows you to stay in VS Code while using your platform's shell, we've added the ability to remove key bindings, and we've made *progress* on Tab support, which you can preview using the [Insiders Release](/insiders).
|
||||
* [**Debugging**](#debugging): You can now control how the Debug Console is revealed and we've improved stepping performance for Node.js applications with large numbers of local variables.
|
||||
* [**Extensions**](#extension-authoring): You can now list, install, and uninstall extensions from the command line. For extension authors, we've expanded our debug, TextMate grammar, and command APIs and we've improved the Language Server Protocol.
|
||||
|
||||
Please continue reading for more information on what's new in May.
|
||||
|
||||
## Editor
|
||||
|
||||
### Trim auto whitespace
|
||||
|
||||
The editor automatically inserts whitespace when you add a new line, based on indenting rules and the previous line's content. Over time, this can result in unnecessary whitespace being persisted in the file. Thanks to [PR #5423](https://github.com/microsoft/vscode/pull/5423), the new `editor.trimAutoWhitespace` setting causes the editor to track the automatic whitespace it inserted and remove it if it no longer is needed, for example by typing somewhere else. Please note, this new setting is on by default.
|
||||
|
||||
|
||||
|
||||
### Select all find matches
|
||||
|
||||
You can now immediately select all find results by pressing `kb(editor.action.selectAllMatches)`. This is much quicker than doing a find and replace and leverages VS Code's multi-cursor support. Thanks for [PR #5715](https://github.com/microsoft/vscode/pull/5715)!
|
||||
|
||||
|
||||
|
||||
### Configure Word Based Suggestion
|
||||
|
||||
When a language service isn't able to compute semantic completion (suggestions), VS Code defaults to word based completions. This is why for some languages you see an IntelliSense list with every word in the file. Some folks would prefer to not see this list at all so you can now disable word based completions with the `editor.wordBasedSuggestions` setting.
|
||||
|
||||
### Resizable Peek View
|
||||
|
||||
The Peek view editor that shows for reference search and for previewing declarations can now be resized!
|
||||
|
||||
|
||||
|
||||
## Workbench
|
||||
|
||||
### Tabs
|
||||
|
||||
> Note: Support for Tabs is **not** in the 1.2.0 (May 2016) Stable release. You can preview the experiences below by using the [Insiders Release](/insiders) of VS Code.
|
||||
|
||||
[Tab support](https://github.com/microsoft/vscode/issues/224) is the number one [User Voice request](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752519-implement-tabs). While the full implementation will take multiple iterations to fully deliver, we wanted to share progress made during the May iteration.
|
||||
|
||||
During this milestone, we focused on managing *stacks* of open editors. In the picture below, you can see that the left pane has two editors open, the center pane has four, and the right pane has two more. Files listed in italics are *preview* files, they allow you to single click and browse files without cluttering the list of open editors and eventually tabs.
|
||||
|
||||
|
||||
|
||||
When you close an editor the last opened editor in the stack is restored, instead of closing the pane as it does today. In addition, we held a number of UX studies that have resulted in further improvements to the design, including:
|
||||
|
||||
* Redesign of the overflow icon
|
||||
* Ability to specify if files from **Quick Open** are pinned or previewed
|
||||
* Added a command to turn a previewed file into a pinned file
|
||||
|
||||
This work has been checked into main and you can preview it using the [Insiders Release](/insiders).
|
||||
|
||||
### Integrated terminal
|
||||
|
||||
[Number two](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752357-integrated-terminal) on User Voice is the request for an integrated terminal, [issue #143](https://github.com/microsoft/vscode/issues/143). It can be convenient to have a terminal embedded directly in the tool, initially scoped to the workspace you are working in. You don't have to switch windows or alter the state of an existing terminal for a quick task.
|
||||
|
||||
With the May release, we are rolling out the initial version of an integrated terminal. You can open the terminal using `kb(workbench.action.terminal.toggleTerminal)`, from the **View** | **Terminal** menu, or from the **View** > **Toggle Terminal** command in the **Command Palette**.
|
||||
|
||||
The shell that is 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. It should act just like the terminal you're familiar with.
|
||||
|
||||
|
||||
|
||||
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 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
|
||||
|
||||
It is now possible to write a key binding rule that targets the removal of a specific default key binding. With the `keybindings.json`, it was always possible to redefine all the key bindings of VS Code, but it can be very difficult to make a small tweak, especially around overloaded keys, such as `kbstyle(Tab)` or `kbstyle(Escape)`. From now on, simply add a `-` to the `command` and the rule will be a removal rule.
|
||||
|
||||
Here is an example:
|
||||
|
||||
```json
|
||||
// In Default Keyboard Shortcuts
|
||||
...
|
||||
{ "key": "tab", "command": "tab", "when": ... },
|
||||
{ "key": "tab", "command": "jumpToNextSnippetPlaceholder", "when": ... },
|
||||
{ "key": "tab", "command": "acceptSelectedSuggestion", "when": ... },
|
||||
...
|
||||
|
||||
// To remove the second rule, for example, add in keybindings.json:
|
||||
{ "key": "tab", "command": "-jumpToNextSnippetPlaceholder" }
|
||||
|
||||
```
|
||||
|
||||
## Languages
|
||||
|
||||
### CSS Variables
|
||||
|
||||
[Variable support in CSS](https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_variables) is a new standards proposal currently in [draft](https://drafts.csswg.org/css-variables/) form. VS Code now supports rich code completion (IntelliSense) for CSS variables as well as Go To Definition, Peek Definition, and Find All Occurrences for variables in the same file.
|
||||
|
||||
For example, here we Peek (`kb(editor.action.peekDefinition)`) at the definition of `--bg-color`:
|
||||
|
||||
|
||||
|
||||
## Linters
|
||||
|
||||
### ESLint
|
||||
|
||||
The [ESLint extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) now supports a "fix all problems" command. You can bind the `eslint.fixAllProblems` command to a keyboard shortcut, such as:
|
||||
|
||||
```json
|
||||
[
|
||||
{ "key": "ctrl+shift+alt+f", "command": "eslint.fixAllProblems",
|
||||
"when": "editorTextFocus" }
|
||||
]
|
||||
```
|
||||
|
||||
### TSLint
|
||||
|
||||
The [TSLint extension](https://marketplace.visualstudio.com/items?itemName=eg2.tslint) now supports excluding files from linting ([PR #47](https://github.com/microsoft/vscode-tslint/pull/47)) as well as quick fixes for a set of TSLint warnings ([PR #40](https://github.com/microsoft/vscode-tslint/pull/40)). Thanks for the pull requests!
|
||||
|
||||
|
||||
## Debugging
|
||||
|
||||
### Control opening the Debug Console
|
||||
|
||||
To provide greater control over how the internal Debug Console is revealed VS Code, we are introducing the `internalConsoleOptions` setting in `launch.json` (see [#6159](https://github.com/microsoft/vscode/issues/6159)). This is especially useful if you are using an external terminal while debugging and you want to keep VS Code focused on your code. The possible values are:
|
||||
|
||||
* `neverOpen` - VS Code will *never* open the debug console
|
||||
* `openOnFirstSessionStart` - VS Code will open the debug console on the *first* debug session
|
||||
* `openOnSessionStart` - VS Code will open the debug console on *every* debug session
|
||||
|
||||
### Node.js Improved Stepping Performance
|
||||
|
||||
We want VS Code to remain lightweight and fast so to improve the stepping experience for programs with a large number of local variables per scope, we've made the following adjustments for Node.js debugging:
|
||||
|
||||
* If a scope has **more than 100 local variables**, VS Code no longer automatically auto expands that scope
|
||||
* After you expand the scope manually, only the **first 100** local variables are shown
|
||||
|
||||
The scope header will reflect that only the first 100 local variables are being displayed:
|
||||
|
||||
|
||||
|
||||
To track a variable that is not within the first 100 you must add it as a Watch expression or evaluate it in the Debug Console.
|
||||
|
||||
## Extension Authoring
|
||||
|
||||
### Debug extension API
|
||||
|
||||
We have exposed a `vscode.startDebug` command as an extension API for the VS Code debugger component. With this, a debug session can be started programmatically either by passing the name of a launch configuration file or a complete launch configuration object:
|
||||
|
||||
```javascript
|
||||
let launchConfig = {
|
||||
type: "node",
|
||||
request: "launch",
|
||||
program: "${workspaceRoot}/test.js",
|
||||
cwd: "${workspaceRoot}"
|
||||
};
|
||||
|
||||
vscode.commands.executeCommand('vscode.startDebug', launchConfig).then(() => {
|
||||
vscode.window.showInformationMessage('Debug session started successfully');
|
||||
}, err => {
|
||||
vscode.window.showInformationMessage('Error: ' + err.message);
|
||||
});
|
||||
```
|
||||
|
||||
More details can be found [here](https://github.com/microsoft/vscode/issues/4615).
|
||||
|
||||
### TextMate grammar injections
|
||||
|
||||
Extensions can now contribute TextMate grammars that inject new rules into the existing grammars used for syntax highlighting. This makes it possible to add colorization inside string literals or comments, such as highlighting of URLs or TODO markers across multiple languages.
|
||||
|
||||
```json
|
||||
"grammars": [
|
||||
{
|
||||
"scopeName": "source.todo",
|
||||
"path": "./syntaxes/todo.tmLanguage.json",
|
||||
"injectTo": [ "source.js", "source.ts" ]
|
||||
}
|
||||
]
|
||||
```
|
||||
|
||||
### Comparing files
|
||||
|
||||
We have added a new API command that allows you to use the diff-editor on two arbitrary resources like so: `commands.executeCommand('vscode.diff', uri1, uri2)`
|
||||
|
||||
### Updated extension samples
|
||||
|
||||
There is a new rich extension sample that walks you through _virtual documents_, _eventing_, and using _language features as commands_. Also, the preview html sample was updated:
|
||||
|
||||
* [contentprovider-sample](https://github.com/microsoft/vscode-extension-samples/tree/main/contentprovider-sample)
|
||||
* [previewhtml-sample](https://github.com/microsoft/vscode-extension-samples/tree/main/previewhtml-sample)
|
||||
|
||||
### Debug Adapter: Support a 'One' or 'All' mode of operation for controlling threads
|
||||
|
||||
In a previous revision of the VS Code Debug Protocol, we had introduced a `allThreadsStopped` attribute on the `StoppedEvent`. With this attribute, a debug adapter can report back to the frontend whether only a single thread or all threads have stopped. Thanks to developer feedback, we learned that a similar attribute is necessary for the `ContinueRequest` too.
|
||||
|
||||
In the version 1.9.0 of the [VS Code Debug Protocol](https://github.com/microsoft/vscode-debugadapter-node), a boolean attribute `allThreadsContinued` has been added to the response from the `ContinueRequest`. Using this attribute, a debug adapter can report back to the UI whether only a single thread or all threads are continuing. More details can be found [here](https://github.com/microsoft/vscode/issues/6400).
|
||||
|
||||
### Language Server Protocol
|
||||
|
||||
The [Language Service Protocol](https://github.com/microsoft/vscode-languageserver-protocol) now offers support for telemetry notifications. Message tracing support has been implemented in the [node client library](https://www.npmjs.com/package/vscode-languageclient) to help tracking down problems in the server. It can be enabled via a settings `${clientName}.trace.server` where client name is the name passed when creating the `LanguageClient` instance. For example `eslint.trace.server` for the ESLint linter service.
|
||||
|
||||
### Command Line Extension Management
|
||||
|
||||
To make it easier to automate and configure VS Code, it is now possible to list, install, and uninstall extensions from the command line.
|
||||
|
||||
Example:
|
||||
|
||||
```
|
||||
code --list-extensions
|
||||
code --install-extension ms-vscode.cpptools
|
||||
code --uninstall-extension ms-dotnettools.csharp
|
||||
```
|
||||
|
||||
## The Monaco Editor
|
||||
|
||||
At the heart of VS Code is the "Monaco" code editor. You can find the "Monaco" editor across many Microsoft properties such as OneDrive, Azure, the TypeScript playground, and even in the F12 tools in IE and Edge.
|
||||
|
||||
Our goal is to enable anyone to consume the "Monaco" editor and host it in any browser. The challenge we have today is that the editor is embedded in the `vscode` repository and the language service extensions have dependencies on client (non browser) technologies.
|
||||
|
||||
The first step towards releasing the editor is [an exploration](https://github.com/alexandrudima/monaco-typescript) where the TypeScript language service has been extracted from VS Code's sources and can run on top of the standalone editor API.
|
||||
|
||||
In the upcoming weeks we will continue to refine the API and automate the packaging with the goal of making the "Monaco" editor public with the June release of VS Code.
|
||||
|
||||
## Notable Bug Fixes
|
||||
|
||||
* [959](https://github.com/microsoft/vscode/issues/959): Fonts become fuzzy after zooming and scrolling
|
||||
* [1000](https://github.com/microsoft/vscode/issues/1000): Slow response when system is offline
|
||||
* [2717](https://github.com/microsoft/vscode/issues/2717): "Define Keybindings" is invalidating keybindings.json
|
||||
* [4541](https://github.com/microsoft/vscode/issues/4541): Problem typing in Korean
|
||||
* [5645](https://github.com/microsoft/vscode/issues/5645): Slow call stack response for TS repository
|
||||
* [5780](https://github.com/microsoft/vscode/issues/5780): Come up with better external terminal defaults on Linux
|
||||
* [6029](https://github.com/microsoft/vscode/issues/6029): debug doesn't work on node v6
|
||||
* [6151](https://github.com/microsoft/vscode/issues/6151): The border of scroll bar is ugly, and unclear under high dpi
|
||||
* [6432](https://github.com/microsoft/vscode/issues/6432): Unity desktop entry not installed immediately after installation
|
||||
* [6525](https://github.com/microsoft/vscode/issues/6525): Linux CLI fails to open files with spaces in filename
|
||||
* [6530](https://github.com/microsoft/vscode/issues/6530): source maps don't work if drive letter case does not match
|
||||
* [6593](https://github.com/microsoft/vscode/issues/6593): Two desktop entries appear on Ubuntu sometimes
|
||||
* [6609](https://github.com/microsoft/vscode/issues/6609): Change keybinding for 'fold all' / 'unfold all'
|
||||
* [6878](https://github.com/microsoft/vscode/issues/6878), [6916](https://github.com/microsoft/vscode/issues/6916): Freeze/Crash when dealing with minified js files
|
||||
|
||||
|
||||
These are the [closed bugs](https://github.com/microsoft/vscode/issues?q=is%3Aissue+label%3Abug+milestone%3A%22May+2016%22+is%3Aclosed) and these are the [closed feature requests](https://github.com/microsoft/vscode/issues?q=is%3Aissue+milestone%3A%22May+2016%22+is%3Aclosed+label%3Afeature-request) for the 1.2.0 update.
|
||||
|
||||
## Downloads
|
||||
|
||||
Downloads: [Windows](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/VSCodeSetup-stable.exe) |
|
||||
[OS X](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/VSCode-darwin-stable.zip) | Linux 64-bit [.zip](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/VSCode-linux-x64-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/vscode-amd64.deb) [.rpm](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/vscode-x86_64.rpm) | Linux 32-bit [.zip](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/VSCode-linux-ia32-stable.zip) [.deb](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/vscode-i386.deb) [.rpm](https://az764295.vo.msecnd.net/stable/809e7b30e928e0c430141b3e6abf1f63aaf55589/vscode-i386.rpm)
|
||||
|
||||
## Thank You
|
||||
|
||||
Last but certainly not least, a big *__Thank You!__* to the following folks that helped to make VS Code even better:
|
||||
|
||||
* [Peng Lv (@rebornix)](https://github.com/rebornix): Add touch screen tap support for reference search. [PR #6386](https://github.com/microsoft/vscode/pull/6386)
|
||||
* [Yuki Ueda (@Ikuyadeu)](https://github.com/Ikuyadeu)
|
||||
* Debt reduction in suggest [PR #6035](https://github.com/microsoft/vscode/pull/6035) and [PR #6057](https://github.com/microsoft/vscode/pull/6057)
|
||||
* Delete the mention [PR #5786](https://github.com/microsoft/vscode/pull/5786)
|
||||
* [Richard Lasjunies (@rlasjunies)](https://github.com/rlasjunies): vscode-tslint - autofix some tslint warnings [PR #47](https://github.com/microsoft/vscode-tslint/pull/47)
|
||||
* [Gary Wilber (@Spacetech)](https://github.com/Spacetech): vscode-tslint - Ability to exclude files [PR #40](https://github.com/microsoft/vscode-tslint/pull/40)
|
||||
* [@dbillingham](https://github.com/dbillingham): [folding] Added fold and unfold recursively to foldings [PR #5721](https://github.com/microsoft/vscode/pull/5721)
|
||||
* [Brian Green (@briangreenery)](https://github.com/briangreenery): Fix small typos [PR #33](https://github.com/microsoft/vscode-languageserver-node/pull/33)
|
||||
* [Rui Lopes (@rgl)](https://github.com/rgl): Correct typos [PR #6](https://github.com/microsoft/vscode-languageserver-protocol/pull/6)
|
||||
* [Brett Cannon (@brettcannon)](https://github.com/brettcannon): Grammar tweak in a comment [PR #8](https://github.com/microsoft/vscode-languageserver-node-example/pull/8)
|
||||
* [Cody Hoover (@hoovercj)](https://github.com/hoovercj): Update launch.json [PR #10](https://github.com/microsoft/vscode-languageserver-node-example/pull/10)
|
||||
* [Yu-Hsin Hung (@hungys)](https://github.com/hungys): Fix link parsing for non-ASCII characters [PR #5293](https://github.com/microsoft/vscode/pull/5293)
|
||||
* [Denis Gladkikh (@outcoldman)](https://github.com/outcoldman): Editor improvements (Implement trim whitespaces on enter, Backspaces decreases indent) [PR #5423](https://github.com/microsoft/vscode/pull/5423)
|
||||
* [@ioklo](https://github.com/ioklo): fix Korean(and Chinese, Japanese) IME behavior [PR #5615](https://github.com/microsoft/vscode/pull/5615)
|
||||
* [aioute Gao (@aioutecism)](https://github.com/aioutecism): Fix validatePosition related bug [PR #5705](https://github.com/microsoft/vscode/pull/5705)
|
||||
* [Asuka (@Inori)](https://github.com/Inori): Add selectAllMatches command in column selection mode [PR #5715](https://github.com/microsoft/vscode/pull/5715)
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:798adff03d96375f0883ccbd19b07b4e6bc5fa338e1ec340d2a56118d144dcbd
|
||||
size 3104
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1d5c5d8c7045c5292055ca54ba93782baca3737caf06aaa33a871f0aa1acfed2
|
||||
size 12607
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fa81e2bbf92eb8681fdafe8b810c2d1f6e326eb4e91f45d824ed27cdd2eacedc
|
||||
size 877
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e5fc25a8e6a1d982542676c942baedf4622ecc3ac11330b2f0a0ccf36b7eb438
|
||||
size 4366
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:03db61480ecf7a2ea7e98e3d4678e01482ffc20fa5b4b8ed307aa9827e1a899a
|
||||
size 110748
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3a4fe1beba75c2a59cbcf0025bd1c56e361faa64a670fbd2d44e8ee03051fd1a
|
||||
size 27521
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0ad32639e9fe04bc44de2f9ffa8259038c838da5cfbaf999c877e0f86c602b73
|
||||
size 54646
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b26cbac05fd672d7397b71e49f05b380c99992bd5e75362c0e1776bbbfc36364
|
||||
size 599
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7765617ba9386508f414070760f23ecd7a299165d4d7b36798253e8da116616f
|
||||
size 10089
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9e28c77e20dad4971bf16456087d9c4b643d2f0d3737b30716f3e2cf8df3de73
|
||||
size 8603
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c5d488d7ebd434185e9e381cf0dab4da74a854e36abba6085c6c34708df14dae
|
||||
size 2098
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c905bf2c6b7e408e15d21e13b1bec04f7cd19e38e7ffa5a53190de7efbf15b4a
|
||||
size 31958
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7a02e6da04db71ec93622459e92c67e612a412208fe8b432b48ef4f8aaba0bbc
|
||||
size 74404
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fa924f890ffa1edade7d6be43efaf415925f2f5395bd0900f34173bcc90c7a00
|
||||
size 52878
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:07bf6347f9eb7c138d7b5c259faad415ea921bc45582eb2b6783e9f0e1ea9e8f
|
||||
size 7608
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:17788637aa1b38e4bc8af2f85d8518dfdd3f8eadd942a12bc985c339a06c60b2
|
||||
size 19153
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:982acc55b277b8fa34abcc06a02707762e40b8f087259e8e5e784d77d7147ae8
|
||||
size 2364
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:633c5982a2b81e9bbc767b98fe5981782c5a2b6b5c81a2f69fd1380e679b4cfe
|
||||
size 6656
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2f51cfa6f6077b68e1a23895f837b44043f2e5038cb57fd8e9d17dc5abbdf366
|
||||
size 3598
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:12f9b79952c09154686174ca2b80167c092c0041b3349974d5bcbf21f08101d2
|
||||
size 5637
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4ea898b5369b235382de8f1054c083f1d870623822857d80d89c9987f3fe5ea8
|
||||
size 6191
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7647a24c2778ed5359d90c82c4a92fabb3518a0c8bca202aba980c36831cf04b
|
||||
size 5937
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0b1475bc0f121d86daeb0a6f776efe88bab55e8d4b4fb22a8f2a05f4e26b9bb2
|
||||
size 6655
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3304ef52841c44cb78d2d69b6a2c1f307bef6033ef2d7af79ccc652e0053188f
|
||||
size 2731
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:36a713d3b8b1bfffc05dc849e9ceb84b1a4c841cc547899a565c20b46cb24cbd
|
||||
size 17056
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9a5dd586d84f0c2ec74ae998ccc3372cf9a284fa802172468e492fc6f0db1aa8
|
||||
size 8052
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d692dbf8892be72ff291d605f00f78e23fdb347e6487707712066a3e1b08b3b8
|
||||
size 7411
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e5c7a0e09f67692732a3e03247f0c3c2740c764ca8f1329a38849b0610a9f8cd
|
||||
size 40382
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6b86cf5e0af6ac59a34c0296a4800b12936b8e81ac9946b4208122d1c48d6476
|
||||
size 19701
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7015dcd3f6233e4544501d40739c3c8c8db63694e8d77a7b3044b307dd00c1bb
|
||||
size 9681
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:12d86380a67bf89661d39b7ddcd57dfdb97a57761562ba7b19ddceb62ce8e176
|
||||
size 9242
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:94e1c22b618481c2d3234987a75950670ac72e4f7fcb558a6f6a0a2c1008cd88
|
||||
size 3656
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6f356c4dbb4117072356c1b6ae5b38f2dcf0122436143f8eca5eba55efa4b4e5
|
||||
size 13559
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:678d741d103d906218f99c33b3f0f1d16d56bca1c41ab557c74bfd021570de62
|
||||
size 5483
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d7725b1319d149d84579a2fb5fb8d7e828cb2356014c3e3e0b3f379ef640d157
|
||||
size 3715
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e05e57fe98310b1dcbf6144fd93bd75aa912d33dd2f286707bae63e2330b3633
|
||||
size 4735
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8c1c9f140f4c7c3c7d4deb8fccb156b236a20acd6f70db96229c5773fdc88087
|
||||
size 10709
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7d265822c0c809732febf3e2523292149c811cc51e4848fff42d1f73547f0cbc
|
||||
size 9316
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:340cbe2110d7204829eba8444d66925abccb66eca2b4528adcccb7776b03e574
|
||||
size 13538
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4b97f6b17a6f3ca952dac1d6d5abf9724ea89cbefb08b9d9cb2f3249ba9d85ca
|
||||
size 37686
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:19ffeb2ef751cfd110248431ff83a2eae94fdb9d03d4dfeb4cce2e189cdf8609
|
||||
size 319750
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:48fe67adef9c92b710ac0dc6be886edf653d73756f539c3165504b38ce2a59b5
|
||||
size 20136
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ace6a0098c5f26d592e24dc8a4d2e08f3d950a71373ed9a16876a58137fafd89
|
||||
size 11692
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4de2f72336deb83c1dde7127d14fb7318742fa632e32f49ea0c6848f101e1db4
|
||||
size 24302
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:66b591200bece2e52a1cdb0a812c8a44581e8151a003ad8c7ef962d9f17edbaa
|
||||
size 4079
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9d60195c3ed09ca395de9f858c4856d8ee49d063529db8e5e859c58943968549
|
||||
size 31172
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:32e5f4e2aeb0036082ac43723469b01cdea44f740beb8905bcca0b5af1ef156a
|
||||
size 96301
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9444e12dbc68eb3bb60c63b9246ac6c2c720d5fc2c316cd6af5d98aaca6d86b0
|
||||
size 23527
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c975668ec0ba672edbfccb18ebbfe834bf22fc1784e1c77da03cc11f6027fa94
|
||||
size 2153
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8ad67f6169bf398c19c8767fa9182a820b983ffae61c40d5b07c4026a55656cf
|
||||
size 2420
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4b5e25178335e5b29995f1dd79861764eef1a19ccd1e10d4add3969e75f4aa53
|
||||
size 3557
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5dc231d6aa7611af3dc8d3ee9bd75ab5b7cd14acabec96531a6e9d9ea71552c3
|
||||
size 21305
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e41a2cb73d60aea9f4df6f4927eb15ee68f8ad90bf828eb483f8a3912523383a
|
||||
size 168489
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:782feb4b352daf2cef9e37e00b21c946cd6a21b0f97512631ddf1a14cbef0373
|
||||
size 822438
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6f1ae8f286a6ffb02a396bd7f1397a1ba879037c17b1b96184c6fe9b21ec3295
|
||||
size 897818
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:82a53c8701e1ce1b60bb0cd54a852ac08f651affde133d965895c379ce7269e8
|
||||
size 43839
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:86f3ded721cf19d38d76885d1a01d8d82d1aeb60e67bacaf750ff3ae1b5304fa
|
||||
size 37833
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:713ae8ae9746f6249a3839d549111cf305645626343f0c00dda9e88a85488aa9
|
||||
size 669662
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bf8922845490407b12d0f5361ad6f35115355c2d3d1db46e38cf120ed61ffe1c
|
||||
size 114538
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0c1efe192d463f3bfe423130d248a7b6f3e52373f1f0368ed7596b716a53dfc6
|
||||
size 51952
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2d7128a316d8fb28cfce80f8d63207d106f35f5bbdabdd6d7db0800cc29990e3
|
||||
size 2911975
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d1cdd9a94420d1a473791962839b020d7abfca48e51473932a3368e17ecdaa19
|
||||
size 687021
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a810fe0144b341f4c2eaf798de0ccaa9bcd7ef3889843732c1b4b413e1ec64f6
|
||||
size 23460
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2086187f2e832eeabf9bc0c69c7f28c5f70c4e8375dba4dcddc970fdd832fcd3
|
||||
size 24296
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:792ad1ab355c69789a64f127d3f44cc4d488e7e26bf9709fce389c99e68b996a
|
||||
size 13492
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:411eaaf6804c3d18d019527e7833b781f9d42674e8079a052f6dca63e89c57d9
|
||||
size 4932
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9d8e92e147bdf8245d21348715d95ba59aee9d337f3989e5cafdd41c721d9637
|
||||
size 153584
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6186769924ccf101058527e6ed5ae22a258689fb3f839ee33f013eb2d2646c91
|
||||
size 21511
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5d14f6492539e646e2aed8760f342082d9485b11fbf9ba944ec5ea63a959177e
|
||||
size 13451
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b717a1958bc6fd4736208e7dba02fd056b1ce3318629dc6f6711cf2b06095121
|
||||
size 721492
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4f077be31b0bc937a4f9bd900789322c16b8520379ae8f252c875f5ba3a6d720
|
||||
size 22299
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:231b85fe5588e790f793f60819263d8d45f5b62e479e5bf5ea1309ca1b636c17
|
||||
size 3579788
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4c388b29b023fd1a49978c807744777781514f7b33139a19499f062cbd9e05ce
|
||||
size 42690
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c9dbb16fc2aac98afcdc1f2d0a8c97cff79f428c4727a12ab57f26c6fd49500a
|
||||
size 76970
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fc823b1582c8e74b3c4a950c37208233734676c2ff1851299936b0844782afaf
|
||||
size 5230
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:12ba49d2b18810283485a29648a6708fa5aa3660420bda230434cdc54e4ab3a3
|
||||
size 108132
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8e6a263fd05ff5bdb5696a37836579507f1f70e16b2bd88e6c00d29a16cf4d5b
|
||||
size 53788
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7ac10f3c0a3ae9410cb7195d15ec1b0b3f955cf01d65b81a8466a7a7cca37673
|
||||
size 9670
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:571c00c05269ca066de994d27c7618b22c0872bb42b2eb4d2a743a7c91ceea36
|
||||
size 1111409
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8755135c7cc5c11d109a7fc582a595e670d6984dd45ade3b058de155af24a7f0
|
||||
size 4603858
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5f6ef48578e9f4124f2084436a725e36ae5937a73e69ceae398c2d94b8b1f71f
|
||||
size 1042767
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:670eca525321d362a2af94cf41b39becea4c0a790449b4da9c492e2ead6fea11
|
||||
size 21949
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7a0c6471daa2d1834646e9cdc12626fbb1ea3e92d6cfd0fe97a7fc111f451a3f
|
||||
size 426
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9b678edfabd7051815f0cdfbb25c0279a41c84f25cf55110c02150d9d04ff22b
|
||||
size 9244
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ad6260586a9a7935b16a5acc87a69b542bd907410bae1336a3379ca68b19dc97
|
||||
size 9857
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:cb2c11d85064c59f099d032962731cfc2945cd1018e42694db3c1699ff3b988d
|
||||
size 7617
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:d419d1152fd6ac415599d7e001fc9efd35e5219190d8d98d557211310e20fdf8
|
||||
size 6350
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bd738bad4e58382318e624c1208dcc3fc3c0b94f79988d77e5574958a40eee4c
|
||||
size 62180
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0a673880957c19b4d4d34675667c7392d5b799fd3d03a5adaeeb0439473a7241
|
||||
size 8878
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9bd41eff4fc8b3d0e048f7bd3a3d1aac7c00ffd563b7dc9cbadd41750821334c
|
||||
size 171963
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:455a4c65f6e2438f5fff8c8709041ba66e29d521480025121357f4f5795f12b0
|
||||
size 946477
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8df568c9f81afd2c12a6619204add67fea5335d0f0d54d863e4e8a19c59d914a
|
||||
size 9113
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8de5df0909f59e3d9a75273b131a6ea55d393953b342d1a9a82c250d23b53fa9
|
||||
size 2895769
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:49b0001ed15e5dc20e209162244cff8b2091b2cfff47a6d83905de4516b1666e
|
||||
size 7495119
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4a093ead1293b521dd8d078f21b59079c1e96e6fec7a2b83de8d2c9f2725176b
|
||||
size 11429
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9b3f0b6d105955d4662118f4ca9cc2c9ba1fd92ba3a58accb23960f559a9fc25
|
||||
size 22955
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e7d71699b2b94955be65a6355461a3f5b9a4a1c4da0cb405c533bfb5f30497b9
|
||||
size 105617
|
||||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче