Can't open hyperlinks in the built-in markdown preview

[SuperSASS]

When I click the hyperlink of [[link]] in the built-in VSCode Markdown preview, it can't be opened because the path of linked file is wrong, as the working directory will be added to the front of the path.

For example:

After I click the hyperlink "Tips" in markdown preview, an error will pop up.

You can find the additional working directory as the underlined part.

• OS: Windows 10 21H1 (The same problem happened in Windows 7, either)
• VSCode version: 1.62.0

I have disabled all extensions for markdown but the problem still remains.

---

However, I found it works fine on my Linux system.

Moreover, I found if I use ![[link]] and click the hyperlink icon on the right, it will open the browser with the address: https://file+.vscode-resource.vscode-webview.net/(file path)

In the system above(Windows 10), nothing happens when click this icon.

[svsool]

Hi, thanks for reporting.

Seems like a Windows specific problem. Last time I tested paths worked fine in preview under Windows, so it could be related to some recent updates in VSCode. Likely logic here and here should be checked.

Do you btw use latest version of this extension?

[SuperSASS]

Yes, I downloaded the extension from VSCode recently, and the version of it is 0.3.9.

[antulik]

I'm experiencing the same issue

Mac Monterey 12.0.1
VS Code Version: 1.62.3
Memo Version: v0.3.9

Unable to open 'People.md': Unable to read file '/Users/anton/work/practice-ignition/knowledge-base/Users/anton/work/ignition/knowledge-base/notes/People.md' (Error: Unable to resolve nonexistent file '/Users/anton/work/ignition/knowledge-base/Users/anton/work/ignition/knowledge-base/notes/People.md').

Notice the folder path is duplicated /Users/anton/work/practice-ignition/knowledge-base

[proItheus]

The same issue in Arch linux : 无法读取文件'/home/proitheus/Documents/vscode-memo/home/proitheus/Documents/vscode-memo/help/Features/Features.md'

[svsool]

Hi, it seems that internal logic for resolving links changed once again in VSCode inside markdown preview.

This problem should be fixed in the latest version of Memo (tested under macOS and Windows). Please update from Marketplace!