UI

[Juergen A. Erhard]

-----BEGIN PGP SIGNED MESSAGE-----

A couple of points:

  + I've checked the docs (as much as there is), but there seems to be
    no explanation on why a simple

    gpg

    `hangs'.  It seems it wants some input (^D terminates).  Why does
    it do that?  Why not just give some short help (less than a
    typical screenful), and terminate?

  + Couldn't some of the commands/options be a little shorter?  Why is
    --list-ownertrust not simply --list-trust?

  + Where's the argument parsing coming from?[1]  Standard GNU
    getopt-long does not need the full option, just enough so it is
    uniquely identified.  Whereas the current parser needs the *full*
    option (--list-secret-keys is nice and long, --list-sec would be
    much nicer to type).

Anyway, thanks for listening,

Bye, J

[1] arparse.c mentions WkLib... I didn't check whether WkLib is
mentioned anywhere else in the sources, but I'm sure I haven't seen it
before.  What *Wk*Lib stands for is anyone's guess ;-)

- -- 
Jürgen A. Erhard  eMail: jae at laden.ilk.de  phone: (GERMANY) 0721 27326
	My WebHome: http://members.tripod.com/~Juergen_Erhard
		 The GNU Project (http://www.gnu.org)
	Win32 has many known work arounds. For example, Linux.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQEVAwUBNi/nlwIG66LugGzRAQHnVwf7BrsLbE43Gj4ukrI+rR4dFVIx+IhTCIs3
/Hr6N27TScpmS55eT4ws4iC8nfcz7MFxK5x85mQ3pBA3SgiM9iD4axsGrAn2R6xE
P2jR2l/WVB74QNnJHHbXQ62pZc8aDaf3k+CNpk4jKgDHmCTQClHxCBS8OW61OQzn
40ABmnjHjl2tJt6OByihMvr06zGk5isWebEGI4nVbj1AqT6JzPIcnTBkpMo4w8km
zw2pg+K8wPKDtts5Ls1LxuNLgBiA5jOudR/iVZ0ZCjSVo/cmJXaWUyGBuAxsKOls
MlEHqKcU5btCP7SXH2T6v2S8lfn/XHE8pVfOGfZda0CnW0KhzgwI0w=
=2tXJ
-----END PGP SIGNATURE-----