Clarification in man page?

Peter Lebbing peter at
Sat Apr 21 11:55:27 CEST 2012

On 20/04/12 16:17, Werner Koch wrote:
>   $ gpg2 foo --armor
>   gpg: NOTE: `--armor' is not considered an option
>   usage: gpg [options] [filename]
> If you really want --armor as a filename, the warning will of course not
> be shown

Why is --armor dropped when it is not wanted as a filename?

> And that is actually the case.  The difference between commands and
> options is that you may only have one command.

I think you misread what I meant :). Confusion all around!

I have this command:

$ gpg2 -a -o foo.asc --export de500b3e

Now if commands and options are equal citizens in the land of the command line,
I think this should also work:

$ gpg2 --export de500b3e -a -o foo.asc

All I did was change the order; the only difference between commands and options
is how many are allowed in one command line. I stuck by the rule as I read it.

However, it doesn't do the same.


I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at

More information about the Gnupg-users mailing list