security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-23 10:29:58 +01:00
Code Activity

* gpg.sgml: Clarify that only long-form options can go in the config file.

Browse Source
This commit is contained in:
David Shaw 2002-08-06 17:22:31 +00:00
parent 111f78b1ff
commit f48650872e
2 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ChangeLog
View File

@ -1,3 +1,8 @@
2002-08-06 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Clarify that only long-form options can go in the
config file.
2002-08-06 Werner Koch <wk@gnupg.org> 2002-08-06 Werner Koch <wk@gnupg.org>
* gpg.sgml: Fixed doc regarding the name change of the option * gpg.sgml: Fixed doc regarding the name change of the option

12
doc/gpg.sgml
View File

@ -706,11 +706,13 @@ all options.
<refsect1> <refsect1>
<title>OPTIONS</title> <title>OPTIONS</title>
<para> <para>
Long options can be put in an options file (default "~/.gnupg/gpg.conf"). Long options can be put in an options file (default
Do not write the 2 dashes, but simply the name of the option and any "~/.gnupg/gpg.conf"). Short option names will not work - for example,
required arguments. Lines with a hash as the first non-white-space "armor" is a valid option for the options file, while "a" is not. Do
character are ignored. Commands may be put in this file too, but that not write the 2 dashes, but simply the name of the option and any
does not make sense. required arguments. Lines with a hash ('#') as the first
non-white-space character are ignored. Commands may be put in this
file too, but that does not make sense.
</para> </para>
<para> <para>
<command/gpg/ recognizes these options: <command/gpg/ recognizes these options: