You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw #66 and #67, but don't understand why installation into the remote container is a requirement for this to work. This is frustrating for two reasons: 1) Where one has control over the remote container, one has to manually install this every time the container is (re)created (no, modifying .devcontainer.json to include an Emacs-specific preference is not an option on a shared, professional project); and 2) Where modification of the remote container is discouraged (i.e., to have as close to a uniform environment as possible), this requires an annoying exception.
Is installation into the remote container really a requirement to get clipboard access? This seems to suggest otherwise?
The text was updated successfully, but these errors were encountered:
I saw #66 and #67, but don't understand why installation into the remote container is a requirement for this to work. This is frustrating for two reasons: 1) Where one has control over the remote container, one has to manually install this every time the container is (re)created (no, modifying
.devcontainer.json
to include an Emacs-specific preference is not an option on a shared, professional project); and 2) Where modification of the remote container is discouraged (i.e., to have as close to a uniform environment as possible), this requires an annoying exception.Is installation into the remote container really a requirement to get clipboard access? This seems to suggest otherwise?
The text was updated successfully, but these errors were encountered: