bold links dont open in markdown file using editor mode with ctrl + click

[ucavalcante]

• VSCode Version: 1.32.1
  05f146c
  x64
  

• OS Version: Windows 10 Pro 1809 build 17763.348

Steps to Reproduce:

1. Open .md file with internet link inside.
2. Press Ctrl + Click in the link
3. See ** on end of the link in web browser.

Does this issue occur when all extensions are disabled?: Yes

bold links don't open in markdown file using editor mode with Ctrl + click I believe the two * in end are sending to the browser, this is don't occurs in preview mode they work properly.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Markdown link provider misses link for image (#49238)
• Add way to open Markdown links in a different editor group (#26659)

[KanteLabs]

@alexr00 @Tyriar If no one is working on this. I would like to take a crack at this.

[ngrygiel]

If this still isn't fixed I'd like to take a look into this.

[KanteLabs]

@ngrygiel you can take a crack at this.

[w9jds]

So, I was looking into this a bit and I found that the regex provided in the actual documentLinkProvider.ts doesn't actually find the link (with or without the bold). So I'm not sure that is where it would be fixed as suggested in the closed PR.

[mjbvz]

VS Code has a standard link detector that detected normal http://... links in text files. (src/vs/editor/common/modes/linkComputer.ts). That is what is kicking in here

One option would be to push all markdown link detection into the markdown extension (into that documentLinkProvider.ts). Those links should override VS Code's built-in detected links. The markdown it parser can find these

Or instead of markdown it, you could try using the vscode.executeLinkProvider command to get the links that VS Code built-in link detector detects and then rewriting the results to not have the trailing *

[w9jds]

Sorry for the delay.

One last question for you. When I looked at the RFC 3986 on Reserved Characters in URIs, it looks like the * is considered one that is required to be encoded, so shouldn't the linkComputer be updated to consider it as a delimiter causing the link to end?