flathub / flathub/com.visualstudio.code

flatpak-run invocations don't share IPC socket

Open
#210 8 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
217
Forks
82
Avg merge
1d 7h
Merged PRs (30d)
1

Description

Visual Studio Code is designed to run as a single process within the session: if you run `code /someproject` and then `code --new-window /some/other/project` the idea is that the second invocation opens `/vscode--.sock` and asks the initial process to open the second window, where:

```
: $XDG_RUNTIME_DIR if set, otherwise the VSCode userDataDir
: a truncated md5sum of userDataDir
: 1.54.2 or whatever
```

But with the Flatpak, every invocation of `flatpak-run com.visualstudio.code` gets a new temporary $XDG_RUNTIME_DIR created.

This makes `alias code="flatpak run com.visualstudio.code"` not work very well.

I don't have a great idea for a solution:

* I've created a workaround wrapper script that uses `flatpak ps` and, if an existing process is found, `flatpak enter` - but `flatpak enter` is more a development facility then something to use in production.
* If the wrapper script unset $XDG_RUNTIME_DIR, then the socket would be created within `~/.var/app/com.visualstudio.code/config/Code/`, which might work OK. I don't think sharing the user data dir on a NFS home directory would work well anyways.
* Some sort of Flatpak feature added to share $XDG_RUNTIME_DIR between `flatpak run` invocations?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.