Man Page UserId Question

[David T-G]

--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Samuel --

=2E..and then Clough, Samuel said...
%=20
% I'm using 1.0.6-2 on NT.
% I was trying to encrypt a file and using the --recipient option and I hav=
e a
% two name id like Bob Smith.  Per the man page, I can enter =3DBob Smith b=
ut it
% did not work.  I tried "Bob Smith" and it appeared to work.  Am I missing
% something or is this a Windows feature?

It's because spaces make things really ugly.  I don't know how the regexp
engine in gpg works, but you might try =3DBob.Smith to turn the space into
a dot and thus not break the two halves into two arguments.  If that
doesn't work you can try escaping the space as =3DBob\ Smith but cmd.exe
might not handle that gracefully.

This behavior isn't limited to Windows, but the problem is more common
there because the GUI shields you from all of the pain and agony of using
spaces, which most *NIX people already recognize as a Very Bad Thing.
Under the covers Explorer has to wrap everything in quotes anyway, and if
quotes are otherwise required then it has to use the silly progra~1 short
name format.


HTH & HAND

:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


--/NkBOFFp2J2Af1nK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9EdV9Gb7uCXufRwARAmZxAJ9wAh/582RT6lNLbTP43lIyCv241ACeK61q
awlPhuiRekl08GBE13lmBjM=
=P3mM
-----END PGP SIGNATURE-----

--/NkBOFFp2J2Af1nK--