Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown Link Definitions: VS Code does not jump to link definition when label includes back-ticks #66

Closed
macdaddie opened this issue Oct 12, 2022 · 0 comments · Fixed by #68
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@macdaddie
Copy link

macdaddie commented Oct 12, 2022

Markdown Link Definitions: VS Code does not jump to link definition when label includes back-ticks

Steps to reproduce the problem

(Please view this in the raw markdown and cut and paste it into VS Code to understand the issue fully)

In the example below, in the This Works example you will see that there is a valid link like under the github symbol and hovering over the symbol gives the tool tip 'Go to Link Definition' and clicking on the symbol will jump you to the bottom of the file and the associated link definition.

Conversly, in the This Doesn't Work example note that the label is surrounded by back-ticks and now the github symbol does not show a tool tip nor can it be clicked on to jump to the associated reference.

However, in preview mode both symbols will correctly redirect you to https://github.com

This Works

[github][github]

This Doesn't Work

[`github`][github]
<!-- links -->
[github]: https://github.com
@mjbvz mjbvz transferred this issue from microsoft/vscode Oct 12, 2022
mjbvz added a commit that referenced this issue Oct 13, 2022
@mjbvz mjbvz added the bug Issue identified by VS Code Team member as probable bug label Oct 13, 2022
@mjbvz mjbvz closed this as completed in #68 Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants