I've encountered your project after I was wondering if there are any alternatives to the awful and extremely unintuitive CLI syntax of current gpg. I've discussed the option of contributing to the upstream GnuPG code an alternative executable that will use the same C functions and library that the executable gpg uses but with a different CLI syntax and git style commands and arguments and not just everything starting with --. It was discussed thoroughly in the gnupg-devel mailing list in these threads: First here and a long time afterwards here.
I just wanted to share with you my design for the new syntax which I've built strictly according to the official documentation of GnuPG. It's in this gist, I hope you'll understand the syntax of it. I've used # for a subcommand a ## for a subcommand's argument etc. Most of the options are named the same as in the original gpg syntax.
Hello,
I've encountered your project after I was wondering if there are any alternatives to the awful and extremely unintuitive CLI syntax of current
gpg
. I've discussed the option of contributing to the upstreamGnuPG
code an alternative executable that will use the same C functions and library that the executablegpg
uses but with a different CLI syntax andgit
style commands and arguments and not just everything starting with--
. It was discussed thoroughly in thegnupg-devel
mailing list in these threads: First here and a long time afterwards here.I just wanted to share with you my design for the new syntax which I've built strictly according to the official documentation of GnuPG. It's in this gist, I hope you'll understand the syntax of it. I've used
#
for a subcommand a##
for a subcommand's argument etc. Most of the options are named the same as in the originalgpg
syntax.