Adding sections
This commit is contained in:
Родитель
3b7f5569da
Коммит
f6c2fec026
|
@ -8,6 +8,7 @@
|
|||
},
|
||||
"markdown.validate.enabled": true,
|
||||
"markdown.validate.ignoredLinks": [
|
||||
"/Download"
|
||||
"/Download",
|
||||
"/insiders"
|
||||
]
|
||||
}
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c31b92f2b92ee574524b2d4203e4915ac9ee148d1a5142af68731a8772c56e19
|
||||
size 10082
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f10a19af46207b75c76be2bb0d13974deec8e3e071c8647ea011a6ea7f1f9900
|
||||
size 85082
|
|
@ -57,9 +57,31 @@ Path IntelliSense can also help you link to headers within the current file or w
|
|||
|
||||
You can disable path IntelliSense with `"markdown.suggest.paths.enabled": false`.
|
||||
|
||||
### Drag and drop to insert links and images
|
||||
### Creating link to a header in another file
|
||||
|
||||
Quickly insert images and file links by dragging and dropping. To start, drag a file from VS Code's explorer over your Markdown code and then hold down `kbstyle(Shift)` to start dropping it into the file. The preview cursor shows where it will be inserted when you drop it.
|
||||
Need to link to a header in another Markdown document but don't remember or want to type out the full file path? Try using workspace header completions! To start, just type `##` in a Markdown link to see a list of all Markdown headers from the current workspace:
|
||||
|
||||
![Suggestions for all Markdown headers in the current workspace](images/Markdown/md-workspace-header-suggestion.png)
|
||||
|
||||
Accept one of these completions to insert the full link to that header, even if it's in another file:
|
||||
|
||||
![Adding a link to the selected header in another file](images/Markdown/md-workspace-header-suggestion-insert.png)
|
||||
|
||||
You can configure if/when workspace header completions show with the `markdown.suggest.paths.includeWorkspaceHeaderCompletions` setting. Valid setting values are:
|
||||
|
||||
- `onDoubleHash` (the default) — Show workspace header completions only after you type `##`.
|
||||
- `onSingleOrDoubleHash` — Show workspace header completions after you type `#` or `##`.
|
||||
- `never` — Never show workspace header completions.
|
||||
|
||||
Keep in mind that finding all headers in the current workspace can be expensive, so there may be a slight delay the first time they are requested, especially for workspaces with lots of Markdown files.
|
||||
|
||||
### Inserting images and links to files
|
||||
|
||||
Use the `Markdown: Insert Image from Workspace` command to quickly add an image in the current markdown file. This command lets you select one or more images to insert from the current workspace.
|
||||
|
||||
Similarly, the `Markdown: Insert Link to File in Workspace` command inserts a link to one or more files that you select in the current workspace.
|
||||
|
||||
You can also insert images and links by dragging and dropping. To start, drag a file from VS Code's explorer over your Markdown code and then hold down `kbstyle(Shift)` to start dropping it into the file. The preview cursor shows where it will be inserted when you drop it.
|
||||
|
||||
![Inserting a Markdown link by dragging and dropping from the explorer](images/Markdown/drop-link.gif)
|
||||
|
||||
|
@ -127,6 +149,16 @@ You can also use `kb(editor.action.rename)` on:
|
|||
* Internal links: `[text](./path/to/file.md)`. This will rename the file `./path/to/file.md` and also update all links to it.
|
||||
* Fragments in links: `[text](./path/to/file.md#my-header)`. This will rename the header in `./path/to/file.md` and also update all links to it.
|
||||
|
||||
### Automatic link updates on file move or rename
|
||||
|
||||
With automatic Markdown link updating, VS Code will automatically update Markdown links whenever a linked to file is moved or renamed. You can enable this feature with the `markdown.updateLinksOnFileMove.enabled` setting. Valid setting values are:
|
||||
|
||||
- `never` (the default) — Don't try to update links automatically.
|
||||
- `prompt` — Confirm before updating links.
|
||||
- `always` — Update links automatically without confirmation.
|
||||
|
||||
Automatic link updating detects renames of Markdown files, images, and directories. You can enable it for additional file types with `markdown.updateLinksOnFileMove.include`.
|
||||
|
||||
## Markdown preview
|
||||
|
||||
VS Code supports Markdown files out of the box. You just start writing Markdown text, save the file with the .md extension and then you can toggle the visualization of the editor between the code and the preview of the Markdown file; obviously, you can also open an existing Markdown file and start working with it. To switch between views, press `kb(markdown.showPreview)` in the editor. You can view the preview side-by-side (`kb(markdown.showPreviewToSide)`) with the file you are editing and see changes reflected in real-time as you edit.
|
||||
|
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c31b92f2b92ee574524b2d4203e4915ac9ee148d1a5142af68731a8772c56e19
|
||||
size 10082
|
|
@ -0,0 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f10a19af46207b75c76be2bb0d13974deec8e3e071c8647ea011a6ea7f1f9900
|
||||
size 85082
|
|
@ -163,6 +163,34 @@ Jupyter extension's Error Renderer is now removed in favor of the builtin Error
|
|||
|
||||
## Languages
|
||||
|
||||
### Markdown workspace header link completions
|
||||
|
||||
Need to link to a header in another Markdown document but don't remember or want to type out the full file path? Try using workspace header completions! To start, just type `##` in a Markdown link to see a list of all Markdown headers from the current workspace:
|
||||
|
||||
![Suggestions for all Markdown headers in the current workspace](images/1_76/md-workspace-header-suggestion.png)
|
||||
|
||||
Accept one of these completions to insert the full link to that header, even if it's in another file:
|
||||
|
||||
![Adding a link to the selected header in another file](images/1_76/md-workspace-header-suggestion-insert.png)
|
||||
|
||||
You can configure if/when workspace header completions show with the `markdown.suggest.paths.includeWorkspaceHeaderCompletions` setting. Valid setting values are:
|
||||
|
||||
- `onDoubleHash` (the default) — Show workspace header completions only after you type `##`.
|
||||
- `onSingleOrDoubleHash` — Show workspace header completions after you type `#` or `##`.
|
||||
- `never` — Never show workspace header completions.
|
||||
|
||||
Keep in mind that finding all headers in the current workspace can be expensive, so there may be a slight delay the first time they are requested, especially for workspaces with lots of Markdown files.
|
||||
|
||||
### Configure preferred file extension style for Markdown links
|
||||
The new `markdown.preferredMdPathExtensionStyle` setting configures if VS Code prefers using file extensions for links to Markdown files. This preference is used for language tools such as [path completions](/docs/languages/markdown.md#path-completions) and [link renames](/docs/languages/markdown.md#rename-headers-and-links).
|
||||
|
||||
Valid setting values are:
|
||||
|
||||
- `auto` — Try to preserve the existing style of the file extension.
|
||||
- `includeExtension` — Include the trailing `.md` in the link.
|
||||
- `removeExtension` — Remove the trailing `.md` from the link.
|
||||
|
||||
|
||||
## Extensions
|
||||
|
||||
## Remote Development
|
||||
|
@ -270,6 +298,15 @@ This release ships the experimental asynchronous tokenization feature. This feat
|
|||
|
||||
For now, asynchronous tokenization is disabled by default and can be enabled by setting `editor.experimental.asyncTokenization` to `true`.
|
||||
|
||||
### TypeScript 5.0 support
|
||||
|
||||
This update includes support for the upcoming TypeScript 5.0 release. See the [TypeScript 5.0 Beta blog post](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0-beta/) and [TypeScript 5.0 iteration plan](https://github.com/microsoft/TypeScript/issues/51362) for more details on what the TypeScript team is currently working on. Some editor tooling highlights:
|
||||
|
||||
* New `switch` and `case` completions help you fill in both sections of `switch` statements more quickly.
|
||||
* Work on enabling project wide IntelliSense on [github.dev](https://github.dev) and [vscode.dev](https://vscode.dev).
|
||||
|
||||
To start using the TypeScript 5.0 nightly builds, install the [TypeScript Nightly](https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next) extension or install the latest [VS Code 1.76+ Insiders build](/insiders).
|
||||
|
||||
## Extension authoring
|
||||
|
||||
### Link support in InputBox prompts and validation messages
|
||||
|
|
Загрузка…
Ссылка в новой задаче