如何在 Markdown 中链接到同一文档的部分内容？

夜声 2024-09-08 11:54:35

Github 自动从标头中解析锚标记。因此，您可以执行以下操作：

[Custom foo description](#foo)

# Foo

在上述情况下，Foo标头已生成一个名为foo的锚标记

注意：只有一个< code># 对于所有标题大小，# 和锚点名称之间没有空格，锚点标签名称必须小写，如果是多个单词，则以破折号分隔。

[click on this link](#my-multi-word-header)

### My Multi Word Header

更新

也可以与 pandoc 一起使用。

Github automatically parses anchor tags out of your headers. So you can do the following:

[Custom foo description](#foo)

# Foo

In the above case, the Foo header has generated an anchor tag with the name foo

Note: just one # for all heading sizes, no space between # and anchor name, anchor tag names must be lowercase, and delimited by dashes if multi-word.

[click on this link](#my-multi-word-header)

### My Multi Word Header

Update

Works out of the box with pandoc too.

回复收藏 0 原文

白昼 2024-09-08 11:54:35

这可能是过时的线程，但要在 Github 中的 markdown 中创建内部文档链接，请使用...
（注意：小写#title）

# Contents
 - [Specification](#specification) 
 - [Dependencies Title](#dependencies-title) 

## Specification
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. 

## Dependencies Title
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah.

提出了一个很好的问题，所以我编辑了我的答案；

可以使用 - #、##、###、####< 建立任何标题大小的内部链接/代码> 我在下面创建了一个快速示例...... https://github.com/aogilvie/markdownLinkTest

This may be out-of-date thread but to create inner document links in markdown in Github use...
(NOTE: lowercase #title)

# Contents
 - [Specification](#specification) 
 - [Dependencies Title](#dependencies-title) 

## Specification
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. 

## Dependencies Title
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah. Example text blah. Example text blah. 
Example text blah. Example text blah.

A good question was made so I have edited my answer;

An inner link can be made to any title size using - #, ##, ###, ####
I created a quick example below...
https://github.com/aogilvie/markdownLinkTest

回复收藏 0 原文

記柔刀 2024-09-08 11:54:35

经过实验，我找到了一个使用的解决方案，但一个明显的解决方案是将您自己的锚点放置在页面中您喜欢的任何位置，因此：

<a name="abcde">

before 和

</a>

在您想要“链接”到的行之后。然后，像这样的 Markdown 链接：

[link text](#abcde)

文档中的任何位置都会将您带到那里。

解决方案插入一个“虚拟”分区只是为了添加 id 属性，这可能会破坏页面结构，但是解决方案应该是无害的。

（PS：将锚点放在您想要链接到的行中可能没问题，如下所示：

## <a name="head1">Heading One</a>

但这取决于 Markdown 如何处理它。例如，我注意到 Stack Overflow 答案格式化程序对此感到满意！）

Experimenting, I found a solution using <div…/> but an obvious solution is to place your own anchor point in the page wherever you like, thus:

<a name="abcde">

before and

</a>

after the line you want to "link" to. Then a markdown link like:

[link text](#abcde)

anywhere in the document takes you there.

The <div…/> solution inserts a "dummy" division just to add the id property, and this is potentially disruptive to the page structure, but the <a name="abcde"/> solution ought to be quite innocuous.

(PS: It might be OK to put the anchor in the line you wish to link to, as follows:

## <a name="head1">Heading One</a>

but this depends on how Markdown treats this. I note, for example, the Stack Overflow answer formatter is happy with this!)

回复收藏 0 原文

带上头具痛哭 2024-09-08 11:54:35

是的，markdown 确实可以做到这一点，但您需要指定名称锚点。

一个完整的示例，

这将创建链接
[tasks](#tasks)

在文档的其他位置，您创建命名锚点（无论它被称为什么）。

<a name="tasks">
   my tasks
</a>

请注意，您也可以将其包裹在标题周围。

<a name="tasks">
### Agile tasks (created by developer)
</a>

yes, markdown does do this but you need to specify the name anchor <a name='xyx'>.

a full example,

this creates the link
[tasks](#tasks)

elsewhere in the document, you create the named anchor (whatever it is called).

<a name="tasks">
   my tasks
</a>

note that you could also wrap it around the header too.

<a name="tasks">
### Agile tasks (created by developer)
</a>

回复收藏 0 原文

芯好空 2024-09-08 11:54:35

在 pandoc 中，如果您在生成 html 时使用选项 --toc，将生成包含各部分链接的目录，并从各部分标题返回到目录。它与 pandoc 编写的其他格式类似，例如 LaTeX、rtf、rst 等。因此，使用命令

pandoc --toc happiness.txt -o happiness.html

这一点 markdown:

% True Happiness

Introduction
------------

Many have posed the question of true happiness.  In this blog post we propose to
solve it.

First Attempts
--------------

The earliest attempts at attaining true happiness of course aimed at pleasure. 
Soon, though, the downside of pleasure was revealed.

将生成 html 正文：

<h1 class="title">
    True Happiness
</h1>
<div id="TOC">
    <ul>
        <li>
            <a href="#introduction">Introduction</a>
        </li>
        <li>
            <a href="#first-attempts">First Attempts</a>
        </li>
    </ul>
</div>
<div id="introduction">
    <h2>
        <a href="#TOC">Introduction</a>
    </h2>
    <p>
        Many have posed the question of true happiness. In this blog post we propose to solve it.
    </p>
</div>
<div id="first-attempts">
    <h2>
        <a href="#TOC">First Attempts</a>
    </h2>
    <p>
        The earliest attempts at attaining true happiness of course aimed at pleasure. Soon, though, the downside of pleasure was revealed.
    </p>
</div>

In pandoc, if you use the option --toc in producing html, a table of contents will be produced with links to the sections, and back to the table of contents from the section headings. It is similar with the other formats pandoc writes, like LaTeX, rtf, rst, etc. So with the command

pandoc --toc happiness.txt -o happiness.html

this bit of markdown:

% True Happiness

Introduction
------------

Many have posed the question of true happiness.  In this blog post we propose to
solve it.

First Attempts
--------------

The earliest attempts at attaining true happiness of course aimed at pleasure. 
Soon, though, the downside of pleasure was revealed.

will yield this as the body of the html:

<h1 class="title">
    True Happiness
</h1>
<div id="TOC">
    <ul>
        <li>
            <a href="#introduction">Introduction</a>
        </li>
        <li>
            <a href="#first-attempts">First Attempts</a>
        </li>
    </ul>
</div>
<div id="introduction">
    <h2>
        <a href="#TOC">Introduction</a>
    </h2>
    <p>
        Many have posed the question of true happiness. In this blog post we propose to solve it.
    </p>
</div>
<div id="first-attempts">
    <h2>
        <a href="#TOC">First Attempts</a>
    </h2>
    <p>
        The earliest attempts at attaining true happiness of course aimed at pleasure. Soon, though, the downside of pleasure was revealed.
    </p>
</div>

回复收藏 0 原文

看轻我的陪伴 2024-09-08 11:54:35

只需遵循 [text](#link) 语法并遵循以下准则：

按原样写入字母（小写）和数字，用
破折号替换空格 -
删除其余内容注意

例如，如果您有以下部分：

# 1. Python

# 2. c++

# 3. c++11

# 4. asp.net-core

您可以使用以下方式添加引用：

[1. Python](#1-python)
[2. c++](#2-c)
[3. c++11](#3-c11)
[4. asp.net-core](#4-aspnet-core)

asp.net-core 如何变为 aspnet-core, 1. python 变为 1-python 等。

Just follow the [text](#link) syntax and follow these guidelines:

write the letters (lowercase) and numbers as they are
replace spaces with dashes -
remove the rest of the characters

So for example if you have these sections:

# 1. Python

# 2. c++

# 3. c++11

# 4. asp.net-core

You can add a reference by using:

[1. Python](#1-python)
[2. c++](#2-c)
[3. c++11](#3-c11)
[4. asp.net-core](#4-aspnet-core)

Note how asp.net-core becomes aspnet-core, 1. python becomes 1-python, etc.

回复收藏 0 原文

素染倾城色 2024-09-08 11:54:35

pandoc 手册解释了如何使用其标识符链接到您的标头。我没有检查其他解析器对此的支持，但据报道它在 github 上不起作用。

可以手动指定标识符：

## my heading text {#mht}

Some normal text here,
including a [link to the header](#mht).

或者您可以使用自动生成的标识符（在本例中为#my-heading-text）。 pandoc 手册中对两者进行了详细解释。

注意：此仅在转换为 HTML、LaTex、ConTeXt、<强>纺织或<强>AsciiDoc。

The pandoc manual explains how to link to your headers, using their identifier. I did not check support of this by other parsers, but it was reported that it does not work on github.

The identifier can be specified manually:

## my heading text {#mht}

Some normal text here,
including a [link to the header](#mht).

or you can use the auto-generated identifier (in this case #my-heading-text). Both are explained in detail in the pandoc manual.

NOTE: This only works when converting to HTML, LaTex, ConTeXt, Textile or AsciiDoc.

回复收藏 0 原文

西瑶 2024-09-08 11:54:35

通用解决方案

这个问题似乎根据 markdown 实现有不同的答案。
事实上，Markdown 官方文档对此主题只字不提。
在这种情况下，如果您想要一个可移植的解决方案，您可以使用 HTML。

在任何标头之前或在同一标头行中，使用某些 HTML 标记定义 ID。
例如：
您将在代码中看到这一点，但在渲染的文档中看不到。

完整示例：

此处查看完整示例（在线且可编辑）。

## Content

* [Chapter 1](#Chapter1)
* [Chapter 2](#Chapter2)

<div id="Chapter1"></div>
## Chapter 1

Some text here.  
Some text here.
Some text here.

## Chapter 2 <span id="Chapter2"><span>

Some text here.  
Some text here.
Some text here.

要测试此示例，您必须在内容列表和第一章之间添加一些额外的空间或减小窗口高度。
另外，不要在 ids 名称中使用空格。

Universal solutions

This question seems to have a different answer according to the markdown implementation.
In fact, the official Markdown documentation is silent on this topic.
In such cases, and if you want a portable solution, you could use HTML.

Before any header, or in the same header line, define an ID using some HTML tag.
For example: <a id="Chapter1"></a>
You will see this in your code but not in the rendered document.

Full example:

See a full example (online and editable) here.

## Content

* [Chapter 1](#Chapter1)
* [Chapter 2](#Chapter2)

<div id="Chapter1"></div>
## Chapter 1

Some text here.  
Some text here.
Some text here.

## Chapter 2 <span id="Chapter2"><span>

Some text here.  
Some text here.
Some text here.

To test this example, you must add some extra space between the content list and the first chapter or reduce the window height.
Also, do not use spaces in the name of the ids.

回复收藏 0 原文

白色秋天 2024-09-08 11:54:35

如果您喜欢想要导航到的标题中的符号，请记住一些其他注意事项...

# What this is about


------


#### Table of Contents


- [About](#what-this-is-about)

- [⚡ Sunopsis](#9889-tldr)

- [:gear: Grinders](#it-grinds-my-gears)

- [Attribution]


------


## ⚡ TLDR


Words for those short on time or attention.


___


## It Grinds my :gear:s


Here _`:gear:`_ is not something like ⚙ or ⛭


___


## ⛤ Attribution


Probably to much time at a keyboard



[Attribution]: #9956-attribution

...诸如 #、;标题字符串中的 、& 和 : 通常会被忽略/删除而不是转义，并且还可以使用引用样式链接使快速使用更容易。

注释

GitHub 支持提交、自述文件等中的 :word: 语法。请参阅要点（来自 rxaviers）如果对使用它们感兴趣的话。

对于现代浏览器来说，几乎所有其他地方都可以使用十进制或十六进制； w3schools 中的备忘单非常方便，特别是如果使用带有符号的 CSS ::before 或 ::after 伪元素更符合您的风格。

奖励积分？

以防万一有人想知道标题中的图像和其他链接如何解析为id...

- [Imaged](#alt-textbadge__examplehttpsexamplecom-to-somewhere)


## [![Alt Text][badge__example]](https://example.com) To Somewhere


[badge__example]:
  https://img.shields.io/badge/Left-Right-success.svg?labelColor=brown&logo=stackexchange
  "Eeak a mouse!"

注意事项

MarkDown 渲染因地而异，所以像...... .

## methodName([options]) => <code>Promise</code>

... GitHub 上将有一个带有 id 的元素，例如...

id="methodnameoptions--promise"

... vanilla 卫生将导致 id ...

id="methodnameoptions-codepromisecode"

...意味着从模板编写或编译 MarkDown 文件要么需要针对一种slugifeing方式，或者为各种聪明方式添加配置和脚本逻辑喜欢清理标题文本的地方。

Some additional things to keep in mind if ya ever get fancy with symbols within headings that ya want to navigate to...

# What this is about


------


#### Table of Contents


- [About](#what-this-is-about)

- [⚡ Sunopsis](#9889-tldr)

- [:gear: Grinders](#it-grinds-my-gears)

- [Attribution]


------


## ⚡ TLDR


Words for those short on time or attention.


___


## It Grinds my :gear:s


Here _`:gear:`_ is not something like ⚙ or ⛭


___


## ⛤ Attribution


Probably to much time at a keyboard



[Attribution]: #9956-attribution

... things like #, ;, &, and : within heading strings are generally are ignored/striped instead of escaped, and one can also use citation style links to make quick use easier.

Notes

GitHub supports the :word: syntax in commits, readme files, etc. see gist(from rxaviers) if using'em is of interest there.

And for just about everywhere else decimal or hexadecimal can be used for modern browsers; the cheat-sheet from w3schools is purdy handy, especially if using CSS ::before or ::after pseudo-elements with symbols is more your style.

Bonus Points?

Just in case someone was wondering how images and other links within a heading is parsed into an id...

- [Imaged](#alt-textbadge__examplehttpsexamplecom-to-somewhere)


## [![Alt Text][badge__example]](https://example.com) To Somewhere


[badge__example]:
  https://img.shields.io/badge/Left-Right-success.svg?labelColor=brown&logo=stackexchange
  "Eeak a mouse!"

Caveats

MarkDown rendering differs from place to place, so things like...

## methodName([options]) => <code>Promise</code>

... on GitHub will have an element with id such as...

id="methodnameoptions--promise"

... where as vanilla sanitation would result in an id of...

id="methodnameoptions-codepromisecode"

... meaning that writing or compiling MarkDown files from templates either requires targeting one way of slugifeing, or adding configurations and scripted logic for the various clever ways that places like to clean the heading's text.

回复收藏 0 原文

怼怹恏 2024-09-08 11:54:35

Markdown 规范中没有这样的指令。对不起。

回复收藏 0 原文

北风几吹夏 2024-09-08 11:54:35

Gitlab 使用 GitLab Flavored Markdown (GFM)

这里“所有 Markdown 渲染的标题都会自动获取 ID”，

可以使用鼠标来：

将鼠标移到标题上
将鼠标移到标题左侧可见的悬停选择器上
复制并保存链接使用鼠标右键单击

例如，在 README.md 文件中，我有标题：

## Boettcher 函数的级数展开公式< /code>

给出了一个链接：

https： //gitlab.com/adammajewski/parameter_external_angle/blob/master/README.md#series-expansion-formula-of-the-boettcher-function

前缀可以删除，所以这里的链接很简单，

file#header

这意味着：

README.md#series-expansion-formula-of-the-boettcher-function

现在可以用作：

[Boettcher 函数的级数展开公式](README.md#series-expansion-formula-of-the-boettcher-function)

也可以手动完成：用连字符替换空格。

实时示例位于此处

Gitlab uses GitLab Flavored Markdown (GFM)

Here "all Markdown-rendered headers automatically get IDs"

One can use mouse to :

move mouse over header
move mouse over hover selector which becoms visible to the left from header
copy and save link using right mouse click

For example in README.md file I have header:

## series expansion formula of the Boettcher function

which gives a link :

https://gitlab.com/adammajewski/parameter_external_angle/blob/master/README.md#series-expansion-formula-of-the-boettcher-function

Prefix can be removed so the link here is simply

file#header

which here means:

README.md#series-expansion-formula-of-the-boettcher-function

Now it can be used as :

[series expansion formula of the Boettcher function](README.md#series-expansion-formula-of-the-boettcher-function)

One can also do it manually: replace spaces with hyphen sign.

Live example is here

回复收藏 0 原文

旧夏天 2024-09-08 11:54:35

它实际上应该有效。我认为你做错的事情是

[a link](# MyTitle)

行不通的，但相反

[a link](#my-title)

它也适用于另一个文档的部分

[a link](./somefolder/somedoc.md#my-title)

VSCode通过在你写这个时为你提供选项来帮助你

It actually should work. I think the think you are doing wrong is that

[a link](# MyTitle)

won't work, but instead

[a link](#my-title)

It also works for sections of another document

[a link](./somefolder/somedoc.md#my-title)

VSCode helps you by offering you options when you write this

回复收藏 0 原文

碍人泪离人颜 2024-09-08 11:54:35

这对我有用：

这里有 GitHub 预览的更长示例： https://gist.github.com/manero6/ a0a67e8f9ebd7028f6fae51c49208b5d

# Title
title blablabla

#### Table of Content

- [First](#first)
- [Second](#second)
- [Third](#third-ᵗᵒᵖ)
- [Fourth](#fourth-)
- [Fifth](#-fifth)

## [First][toc]
1st

## [Second][toc]
2nd

## Third [ᵗᵒᵖ][toc]
3rd

## Fourth [^][toc]
4th

## [^][toc] Fifth
5th

[toc]: #table-of-content "go to Table of Content"

This works for me:

Longer example with GitHub preview here: https://gist.github.com/manero6/a0a67e8f9ebd7028f6fae51c49208b5d

# Title
title blablabla

#### Table of Content

- [First](#first)
- [Second](#second)
- [Third](#third-ᵗᵒᵖ)
- [Fourth](#fourth-)
- [Fifth](#-fifth)

## [First][toc]
1st

## [Second][toc]
2nd

## Third [ᵗᵒᵖ][toc]
3rd

## Fourth [^][toc]
4th

## [^][toc] Fifth
5th

[toc]: #table-of-content "go to Table of Content"

回复收藏 0 原文

冷夜 2024-09-08 11:54:35

除了上述答案之外，

在 YAML 标头中设置选项 number_sections: true 时：

number_sections: TRUE

RMarkdown 将为您的部分自动编号。

要引用这些自动编号的部分，只需将以下内容放入 R Markdown 文件中：

[My Section]

其中 My Section 是部分的名称

这似乎与部分无关level:

# 我的部分

## 我的部分

### 我的部分

In addition to the above answers,

When setting the option number_sections: true in the YAML header:

number_sections: TRUE

RMarkdown will autonumber your sections.

To reference those autonumbered sections simply put the following in your R Markdown file:

[My Section]

Where My Section is the name of the section

This seems to work regardless of the section level:

# My section

## My section

### My section

回复收藏 0 原文

自由范儿 2024-09-08 11:54:35

使用 kramdown，看起来效果很好：

[I want this to link to foo](#foo)
....
....
{: id="foo"}
### Foo are you?

我看到有人提到它

[foo][#foo]
....
#Foo

可以有效地工作，但前者可能是除了标题或具有多个单词的标题之外的元素的一个很好的替代方案。

Using kramdown, it seems like this works well:

[I want this to link to foo](#foo)
....
....
{: id="foo"}
### Foo are you?

I see it's been mentioned that

[foo][#foo]
....
#Foo

works efficiently, but the former might be a good alternative for elements besides headers or else headers with multiple words.

回复收藏 0 原文

染墨丶若流云 2024-09-08 11:54:35

由于 MultiMarkdown 在评论中被提到作为一个选项。

在 MultiMarkdown 中，内部链接的语法很简单。

对于文档中的任何标题，只需以 [heading][] 格式给出标题名称即可创建内部链接。

在此处阅读更多信息：MultiMarkdown-5 交叉引用。

交叉引用

一个经常要求的功能是让 Markdown 自动处理文档内链接，就像处理外部链接一样轻松。为此，我添加了将 [Some Text][] 解释为交叉链接的功能（如果存在名为“Some Text”的标头）。

例如，[元数据][] 将带您到 # 元数据（或任意 ## 元数据、### 元数据、#### 元数据、##### 元数据、######元数据）。

或者，您可以添加您选择的可选标签，以帮助消除多个标题具有相同标题的情况的歧义：

### 概述 [MultiMarkdownOverview] ##

这允许您使用 [MultiMarkdownOverview] 专门引用此部分，而不是另一个名为“概述”的部分。这适用于 atx 或 settext 样式的标头。

如果您已经使用标头使用的相同 ID 定义了锚点，则定义的锚点优先。

除了文档中的标题之外，您还可以提供图像和表格的标签，然后也可以将其用于交叉引用。

回复收藏 0 原文

沒落の蓅哖 2024-09-08 11:54:35

关于技巧的更多旋转：

<a id="a-link"></a> Title
------

#### <a id="a-link"></a> Title (when you wanna control the h{N} with #'s)

Some more spins on the <a name=""> trick:

<a id="a-link"></a> Title
------

#### <a id="a-link"></a> Title (when you wanna control the h{N} with #'s)

回复收藏 0 原文

零度℉ 2024-09-08 11:54:35

就我而言，我正在寻找一个没有 Pandoc 的 TOC 解决方案。每个 TOC 条目都包含一个指向标题的链接，格式为 [显示名称](#-url-formatted-name-of-header)

对于 2 级缩进的简单情况，

1. [Installation](#1-installation)  
1.1. [Minimum System Requirements](#11-minimum-system-requirements)  
1.2. [Prerequisites](#12-prerequisites)

结果为：

安装< br>
1.1.最低系统要求
1.2.先决条件

对于包含 3 级或更多缩进级别的一般多级编号列表，该列表无法在 3 级或更高级别进一步缩进（例如 1.3.2.）。相反，我能找到的最佳解决方案是使用 >>> 使用嵌套块引号进行格式化。

## Table of Contents  
>1. [Installation](#1-installation)  
>>1.1. [Minimum System Requirements](#11-minimum-system-requirements)  
>>1.2. [Prerequisites](#12-prerequisites)  
>>>1.2.1. [Preparation of Database Server](#121-preparation-of-database-server)  
>>>1.2.2. [Preparation of Other Servers](#122-preparation-of-other-servers)  
>>  
>>1.3. [Installing – Single Server](#13-installing-single-server)  
>>1.4. [Installing – Multi Server](#14-installing-multi-server)  
>>>1.4.1. [Database Server](#141-database-server)  
>>>...

在 GitHub 上生成精美呈现的目录。如果没有 SO 的 linter 抱怨未格式化的代码，就无法在这里渲染它。

注意1.2.2后面的空白条目。
如果没有空白条目，您的以下行将停留在第三个块引用缩进级别。

与仅使用空格或制表符作为缩进标记“正常工作”的项目符号列表进行对比 -

## Table of Contents  
- [Installation](#1-installation)  
  - [Minimum System Requirements](#11-minimum-system-requirements)  
  - [Prerequisites](#12-prerequisites)  
    - [Preparation of Database Server](#121-preparation-of-database-server)  
    - [Preparation of Other Servers](#122-preparation-of-other-servers)  
  - [Installing – Single Server](#13-installing-single-server)  
  - [Installing – Multi Server](#-installing-multi-server)  
    - [Database Server](#141-database-server)  
    - ...

结果：

## Table of Contents  
>1. [Installation](#1-installation)  
>>1.1. [Minimum System Requirements](#11-minimum-system-requirements)  
>>1.2. [Prerequisites](#12-prerequisites)  
>>>1.2.1. [Preparation of Database Server](#121-preparation-of-database-server)  
>>>1.2.2. [Preparation of Other Servers](#122-preparation-of-other-servers)  
>>  
>>1.3. [Installing – Single Server](#13-installing-single-server)  
>>1.4. [Installing – Multi Server](#14-installing-multi-server)  
>>>1.4.1. [Database Server](#141-database-server)  
>>>...

Results in a nicely rendered TOC on GitHub. Can't render it here without SO's linter complaining about unformatted code.

Note the blank entry after 1.2.2.
Without the blank entry your following lines remain stuck at the 3rd blockquote indent level.

Contrast that with bulleted lists which "just work" using only spaces or tabs as indent markers -

## Table of Contents  
- [Installation](#1-installation)  
  - [Minimum System Requirements](#11-minimum-system-requirements)  
  - [Prerequisites](#12-prerequisites)  
    - [Preparation of Database Server](#121-preparation-of-database-server)  
    - [Preparation of Other Servers](#122-preparation-of-other-servers)  
  - [Installing – Single Server](#13-installing-single-server)  
  - [Installing – Multi Server](#-installing-multi-server)  
    - [Database Server](#141-database-server)  
    - ...

Results in:

第一个是 [Part 1.](#1-helm)和[Part 1.1](#11-what-is-helm)，后者自动将普通文本超链接到这些章节。如果使用 VS Code，放置光标并耐心等待，应该会显示一个带有超链接章节的下拉菜单。我认为在执行对其他章节的引用时，应删除空格以及数字之间的 . （如 ## 1.1 What is helm 中的情况）。

回复收藏 0 原文

如何在 Markdown 中链接到同一文档的部分内容？

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

评论（20）

更新

Update

通用解决方案

完整示例：

Universal solutions

Full example:

奖励积分？

注意事项

Bonus Points?

Caveats

交叉引用

Cross-References

目录

Table of Contents

关于作者

相关话题

热门标签

推荐作者

胡图图

zt006

z祗昰~

冰葑

野の

天空

友情链接

如何在 Markdown 中链接到同一文档的部分内容？

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

评论（20）

更新

Update

通用解决方案

完整示例：

Universal solutions

Full example:

奖励积分？

注意事项

Bonus Points?

Caveats

交叉引用

Cross-References

目录

Table of Contents

关于作者

相关话题

热门标签

推荐作者

胡图图

zt006

z祗昰~

冰葑

野の

天空

友情链接

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。