Support GFM style #kebab-case-heading-slug anchor targets

[garthk]

Use case or problem

I’m trying to use Obsidian to browse and maintain a repository of related documents that link to each other in a way compatible with GitHub, Bitbucket, VS Code, and internal tools:

## This is an Internal Heading

[This is a link to the internal heading](#this-is-an-internal-heading)

If I try to follow such a link in Obsidian, it fails:

Unable to find selection in this-document-filename

If I alter the links to use Obsidian’s preferred anchor target, users of other tools can’t follow the links:

[This link to the internal heading works in Obsidian only](#This%20is%20an%20Internal%20Heading)

Proposed solution

I’d like a repository setting useSlugsForHeadingAnchors which, if set true, altered Obsidian’s behaviour to:

• Generate a slug for each heading in a manner compatible with GitHub’s Markdown rendering
• Render headings with an anchor using that slug
• Render inserted links with a target using that slug

Example rendered output given our original Markdown might be:

<h2><a id="this-is-an-internal-heading">This is an Internal Heading</a></h2>

<a href="#this-is-an-internal-heading">This is a link to the internal heading</a>

Current workaround (optional)

I can’t find a workaround.

Related feature requests (optional)

I can’t find related feature requests.

[ItsIgnacioPortal]

So, basically, github-compatible links, right?

[Jiiim]

Yes please! Can we have this?

Super convenient.

[drewm-jpl]

I would really appreciate this feature as well.

[ichimga]

Hi, same here. Also would be great to have support for GFM, perhaps parallel to Obsidian native markdown and be able to choose which one to use.

[leventov]

This feature would be essential for integration with Docusaurus, too.

[grigoresculiviu]

I am adding one point to this topic.
Currently all markdown editors I am familiar with, including Github, Gitlab, Stackedit, IntelliJ, and Visual Studio Code, all support #dash-style-links.

That makes it very difficult for me to move my notes collection to Obsidian as I will loose the references in the process.

Maybe we can have a configuration that allows us to chose the format of the links.

[bnemrk]

I too would find this extremely helpful. As a new user importing my collection of markdown files, none of my tables of contents within notes are usable in Obsidian, but they do work on github, gitlab, bitbucket etc. It seems most other markdown → html renders do automatic anchors to headings this way by default.

Another feature request also mentioned this a short while later: Publish: Support for lowercase and kebab-case slugs in URLs

[jeetsukumaran]

I, too, would like this.

If this feature is implemented, I would love to see an add-on feature where the link is rendered as the original non-normalized heading/title etc. in preview mode?

That is, if linking to heading:

## The Rain in Spain Falls Mainly on the Plains

by

For more details see: [[doc2#the-rain-in-spain-falls-mainly-on-the-plains]]

we would see

For more details see: The Rain in Spain Falls Mainly on the Plains

(I know we can get the same effect by titling the link with an alias, so maybe I can just settle for that )

[jmkim]

+1

It would be nice if kebab-case header ids become the default for Markdown links, unlike Wikilinks.

Related feature requests:

Unique links to headings (no Wikilinks)

Use case or problem I use Markdown links (no Wikilinks) within my vault. I often create a TOC (Table of Content) to link to specific headings in the same file. I start typing [[, followed by # to see a list of headings in that file. These relative links work in general, but there are some cases when they don’t. For example, if the note headings are: ## Header - Example ### A subtitle? ## Another Topic ### A subtitle the links I get are: - [Header - Example](#Header%20-%20Example) - […

GitHub-friendly header links

Use case or problem Since most people use GitHub to store their Obsidian Vaults, compatibility with GitHub’s markdown conventions should be paramount. Ensuring maximum compatibility with GitHub makes it much easier to share vault contents with others. Instead of needing to download and install Obsidian, clone the repository and open the vault locally, they can just view the contents in GitHub’s native UI. Obsidian markdown is already extremely GitHub-friendly, but internal links to headers are…

[jmkim]

Another related feature request:

Support the Github anchor format

Use case or problem As we know, Github support markdown viewing directly in their web pages, so I just uploaded my notes to it and found some errors about anchor. if you type [[# and choose a title with blank and use autocompletion, you will get an anchor with a URLEncoded format %20. If you change it to -, you can jump to proper position in Github and other viewers accepting this format but will fail in Obsidian. An Example: # Anchor Test(test) Obsidian autocomplete: [Anchor Test(test)](#An…

[blue_emperor]

Is implicit header identification in GFM documented somewhere? In GitHub Flavored Markdown Spec header id‑attributes are not documented.

In Pandoc’s markdown spec implicit header references are documented for example—although Obsidian is not intended to support Pandoc’s markdown. If only text is used without GUI−tools, then implicit header references are not optimal since you must write them verbosely. In such cases custom attributes offer really nice solution. Pandoc’s custom attributes syntax:

## heading etc {#identifier .class .class key=value key=value}

## my heading test test test test {#my-heading}

[link to my heading](#my-heading)

I think Obsidian’s block identifiers syntax ## heading ^block-id is similar to above although linking takes different syntax #^block-id and not #block-id.