-
Notifications
You must be signed in to change notification settings - Fork 71
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
integrated-terminal (x86_64-unknown-linux-gnu) #62
Comments
It will never match the host as it isn't the host. |
+1 |
+1
|
On a related note, should there be a warning on where to report issues when using the Flatpak? I imagine upstream VS Code might get a little tired of issues that don't exist on their end past a certain point... |
Isn't this a duplicate of #39 ? |
I seem it's related, but not the same. In any case, VSCode have to not use flatpack until solving this global problem. |
Maybe because Flatpak runs vscode in a container so that vscode isn't able to access commands in the host machine? I am new to Flatpak and I don't understand it very well. |
Use "terminal.integrated.shell.linux": "flatpak-spawn",
"terminal.integrated.shellArgs.linux": ["--host", "bash"], |
This works, however it prints: |
You can ignore the messages or use |
Came from microsoft/vscode#62532
VS Code under flatpack is not workable for complex projects, while with a separate installation everything is fine.
In the OS terminal:
In the VSCode integrated under flatpack:
There is only one object (really 3) and it has different name -
x86_64-unknown-linux-gnu
instead correctx86_64-linux-gnu
. As result - cannot to build library.The text was updated successfully, but these errors were encountered: