On Tue, 24 Feb 2015 00:59, dani...@grinta.net said:
However, the ordering is not really enforced: this
Right. Options and commands are actuallay interchangeable but that is
an undocumented features. In fact the only difference between a command
and an option is that tehre may only be one
On 24/02/15 09:34, Werner Koch wrote:
No, we can't error out on an arg which looks like an option because that
may actually be a valid argument.
However, if running interactively and --batch is not specified, might it
be useful to print Warning: --export-options did not match any key
with the
On 24/02/15 09:34, Werner Koch wrote:
I find it surprising that unrecognized tokens are simply ignored.
Wouldn't it be preferable to error out, at least on unrecognized options?
GnuPG does not follow the common GNU model of interchangeable options
and args. It is modeled like a classic Unix
Hello,
I've been struggling quite a long while today trying to understand why
the following command does not do what I expected:
gpg --export-secret-subkeys 41E999D7! \
--export-options export-reset-subkey-passwd
It does not reset the password on the exported subkey.
After some head
On 24/02/15 00:19, Doug Barton wrote:
On 2/23/15 2:51 PM, Daniele Nicolodi wrote:
Hello,
I've been struggling quite a long while today trying to understand why
the following command does not do what I expected:
gpg --export-secret-subkeys 41E999D7! \
--export-options
On 2/23/15 2:51 PM, Daniele Nicolodi wrote:
Hello,
I've been struggling quite a long while today trying to understand why
the following command does not do what I expected:
gpg --export-secret-subkeys 41E999D7! \
--export-options export-reset-subkey-passwd
It does not reset the password
