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
Love your extension. Recently I switched from using 'nix to manage GPG records to native Windows binaries so I could use a smart card. This extension works perfectly fine in WSL as long as GPG binaries are installed in WSL. It's a whole lotta different story when (as a VSCode WSL user) those binaries are located in Windows.
These two PRs I did internally in my fork address (most) of the cross-compatibility issues I picked up: AlexanderAllen#6, AlexanderAllen#10 (trigger warning, it's a significant rewrite of the gpg module).
However, after those two PRs Assuan rightfully refuses to talk to a naked Windows socket path. That's not exactly a priority for me because the extension is working for my use case, but the ticket is open nevertheless and chances are I might take a bite at it, at some point.
Just thought I'd dropped some visibility into the work I did for supporting WSL users.
I'm not sure about issuing a PR against the main repo quite yet, at least not until cross platform compatibility is in a more production-ready state (see Assuan, above).
But I can drop an update here and there in this ticket as I complete my own PRs, if you'd like.
Cheers!
The text was updated successfully, but these errors were encountered:
Hi @wdhongtw,
Love your extension. Recently I switched from using 'nix to manage GPG records to native Windows binaries so I could use a smart card. This extension works perfectly fine in WSL as long as GPG binaries are installed in WSL. It's a whole lotta different story when (as a VSCode WSL user) those binaries are located in Windows.
These two PRs I did internally in my fork address (most) of the cross-compatibility issues I picked up: AlexanderAllen#6, AlexanderAllen#10 (trigger warning, it's a significant rewrite of the
gpg
module).However, after those two PRs Assuan rightfully refuses to talk to a naked Windows socket path. That's not exactly a priority for me because the extension is working for my use case, but the ticket is open nevertheless and chances are I might take a bite at it, at some point.
Just thought I'd dropped some visibility into the work I did for supporting WSL users.
I'm not sure about issuing a PR against the main repo quite yet, at least not until cross platform compatibility is in a more production-ready state (see Assuan, above).
But I can drop an update here and there in this ticket as I complete my own PRs, if you'd like.
Cheers!
The text was updated successfully, but these errors were encountered: