VS Code multi-root workspace cross-references

[freenandes]

Is it possible for the extension to fetch the theme from a root folder that is not the open folder (with the *.md)?

I'm trying all possible combinations and looking to prevent typos, but i cannot get the relative path to the theme on another root folder.

workspace
 │  
 ├—rootFolderA
 │  └—content.md
 │  
 └—rootFolderB
    └—theme.css

I tried

• the recommended, i think ${workspaceFolder:rootFolderB}/theme.css
• rootFolderB/theme.css
• ../rootFolderB/theme.css
• ../../rootFolderB/theme.css
• ...

Is it not supported? Any strategy to achieve this?

[yhatt]

No, that is not supported.

The path resolution rule for custom theme settings in Marp for VS Code follows the configuration of the standard Markdown preview in VS Code: markdown.styles. Due to potential security issues, both settings do not allow using the style across different workspace roots.

• Can't custum markdown style microsoft/vscode#45260 (comment)
• Could not load 'markdown.styles': *.css microsoft/vscode#77290 (comment)
• Could not load markdown.styles microsoft/vscode#96201
• The markdown.styles stylesheet must be contained inside the current workspace. microsoft/vscode#99280
• Could not load 'markdown.styles' outside workspace microsoft/vscode#101991

— https://github.com/orgs/marp-team/discussions/115#discussioncomment-7435455

[freenandes]

oh... Thanks anyway 🙌

[freenandes]

Before, I had created a workspace made from folderA and then added folderB to it, making both folders workspace roots in a concept in VS Code called multi-root workspace. This won't work with Marp, as pointed in the replies.

I actually had to create a new workspace folder, and then move both folders into it, each with its git.

workspace
│  
└—workspaceRoot
  │ 
  ├—folderA
  │ │ 
  │ └—content.md
  │ 
  └—folderB
    │ 
    └—theme.css

So the reference would simply be folderB/theme.css for this workspace.

This is fine and it works on most extensions. Git works fine.