Update:
I prevent the sync with the "settingsSync.ignoredSettings".
Thank you.
~~(Before submitting this, I am sure that
built-in X11 forwarding does not work.
Many users of the builtin extension reported X11 issues.)
The problems I met.
I am using VS code on multiple devices.
One of them is Windows and one is Linux.
Syncing "Remote X11.SSH: Private Key" brings key reading errors.
On Windows, I use a RSA/PEM format Key,
because the default OPENSSL id_rsa is not supported by "Remote X11".
So I config Remote X11.SSH: Private Key to "~/.ssh/id_rsa.pem"
On Linux, I have to use an OPENSSL Private key (id_rsa) by default
and also make a PEM id_rsa.pem for Remote X11,
but Remote X11 does not support id_rsa.pem and requires id_rsa.
The problem is the path to the Private Key is synced.
If I setup Windows VS code properly,
the synced settings will not work on Linux.
And, vice versa.
The solutions may be:
Do not sync "Remote X11.SSH: Private Key" settings
"Remote X11.SSH: Private Key" support multiple PATH,
and find the key in all stored paths before report errors.~~
Update: I prevent the sync with the "settingsSync.ignoredSettings". Thank you.
~~(Before submitting this, I am sure that built-in X11 forwarding does not work. Many users of the builtin extension reported X11 issues.)
The problems I met. I am using VS code on multiple devices. One of them is Windows and one is Linux. Syncing "Remote X11.SSH: Private Key" brings key reading errors. On Windows, I use a RSA/PEM format Key, because the default OPENSSL id_rsa is not supported by "Remote X11". So I config Remote X11.SSH: Private Key to "~/.ssh/id_rsa.pem"
On Linux, I have to use an OPENSSL Private key (id_rsa) by default and also make a PEM id_rsa.pem for Remote X11, but Remote X11 does not support id_rsa.pem and requires id_rsa.
The problem is the path to the Private Key is synced. If I setup Windows VS code properly, the synced settings will not work on Linux. And, vice versa.
The solutions may be: