wdhongtw
Support for WSL users using Win32 GPG binaries
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: https://github.com/AlexanderAllen/vscode-gpg-indicator/pull/6, https://github.com/AlexanderAllen/vscode-gpg-indicator/pull/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!
Sorry for the late response. To be honest, I lost the motivation to enhance this project last year.
Back to your question. I have fix two critical issue that prevent user from using this extension in Windows. One is CR LF issue, which is also fixed in your fork. Another is the Assuan protocol you mentioned, which is fixed in #77 .
But for the use-case you mentioned: VSCode in WSL using bash shell and launch gpg toolchain in Windows host, is probably hard to solve completely. That should be a general problem for any extension that spawn a binary command to complete the required task.
If you are still interested in this, maybe we can begin with some survey of potential solutions and have discussion accordingly.
Thanks for providing such insight to this project. :D
