-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Unable to export in Flatpak VSCode #451
Comments
{
"markdown.marp.chromePath": "/var/lib/flatpak/exports/bin/com.google.Chrome"
} Related |
Hi @yhatt , thanks for your quick response!
The proposed workaround would work if VSCode was not a Flatpak and Chrome was, but wont work when both of them are. This is by design, see Allow a flatpak to discover/call another flatpak #283 |
Thank you for more context to recognize the problem. By the design of flatpak as you've described, using flatpak Chrome from flatpak VS Code to export Marp slides would be difficult for now. It looks like able to spawn Chrome process, by making the wrapper shell script like below and setting its path to The example of wrapper script (Click to open)#!/bin/sh
flatpak-spawn --host /var/lib/flatpak/exports/bin/com.google.Chrome "$@" If there were the SDK Extension of freedesktop.org for Chrome/Chromium, this problem may be solved because the browser will be available in inside of the VS Code flatpak sandbox. This is already feedbacked to the Flathub community through Obsidian Marp Slides plugin, but there is no progress. |
The wrapper works! Thanks |
Is there a way to export slides in the Flatpak version of VSCode?
I am able to run i.e.: Chrome from the Flatpak vscode version:
However unfortunately the following setting does not seem to work:
The text was updated successfully, but these errors were encountered: