Re: uuencode manpage

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------3383fbcea5216ed70e0d6afcbab5c4b56f73c561875e7631e771f37632417ae1
Content-Type: multipart/mixed; boundary="---------------------a0f8d852d7410bef1a2b222c7b5dff91"

-----------------------a0f8d852d7410bef1a2b222c7b5dff91
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Exactly, no issue with the program itself.

\-- R. Bazaud

\-------- Message d'origine --------
Le 11 sept. 2021 =C3=A0 12:18, Davide Brini < dave\[email protected] > a =C3=A9cr=
it :

>
>
>
> On Fri, 10 Sep 2021 16:38:15 -0700, Bruce Korb <[email protected]> wrote:
>
> > Hello,
> >
> > This is not exactly a response to the issue because I cannot figure out
> > what the issue actually is. This email reads like there should be an
> > antecedent email, but I cannot find it.
> >
> > Anyway, output goes to stdout, period, full stop. What you provide as
> > the final argument to the command is the name encoded into the output
> > file that gets "printed" to stdout. Attached is the POSIX description
> > for the final argument to uuencode.
> >
> > Does that answer your question?
>
> I think what the OP meant is that in the text of the man page, "-"
> could be used in place of "/dev/stdout" since it works the same and it's
> shorter.
>
> \--
> D.
>
-----------------------a0f8d852d7410bef1a2b222c7b5dff91
Content-Type: application/pgp-keys; name="publickey - EmailAddress([email protected]) - 0x44685C95.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - EmailAddress([email protected]) - 0x44685C95.asc"

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tClZlcnNpb246IEdvcGVuUEdQIDIu
MS45CkNvbW1lbnQ6IGh0dHBzOi8vZ29wZW5wZ3Aub3JnCgp4ak1FWUZDc014WUpLd1lCQkFIYVJ3
OEJBUWRBT2NNZkpNOHVPSWVPTnB6M3RyVUl2MVE4czJrd21zWDVGQWN0CnZIMmc2dGpOSFhKaVlY
cGhkV1JBY0cwdWJXVWdQSEppWVhwaGRXUkFjRzB1YldVK3dvOEVFQllLQUNBRkFtQlEKckRNR0N3
a0hDQU1DQkJVSUNnSUVGZ0lCQUFJWkFRSWJBd0llQVFBaENSQTBDeFBFQVVZVS9SWWhCRVJvWEpX
MwpNT2tVRXVEa2lUUUxFOFFCUmhUOVZFWUJBTXRPeHdXTmlITElETGtsM2lxcWVBcFZkNklrR09v
VTZ0a3YzSjFFCnNoRFNBUUQyR290Q1VadnlBZXNXam4zbHU2bzlpRHN1d0NxVkRJaGQ1Z1psVThZ
eEI4NDRCR0JRckRNU0Npc0cKQVFRQmwxVUJCUUVCQjBBbkJNVnBlL1RBSkxkb2Y4dS9FUFpsWjZn
cktSSUZKZEVsYXg4ZHlvVlVPd01CQ0FmQwplQVFZRmdnQUNRVUNZRkNzTXdJYkRBQWhDUkEwQ3hQ
RUFVWVUvUlloQkVSb1hKVzNNT2tVRXVEa2lUUUxFOFFCClJoVDlyT0VBLzB0ZDlOUjRpZ2RLUWow
WGM2Z3RSYUZpcnFKK2YzM0cxcVZyaGJ5RmFJVklBUUQvSGt3NDZVbnUKcTR6ZG8rZ3lTQldjeWRJ
bUpqL1gwMll2UkJKaEZ1V1VDZz09Cj1leEowCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NL
LS0tLS0=
-----------------------a0f8d852d7410bef1a2b222c7b5dff91--

--------3383fbcea5216ed70e0d6afcbab5c4b56f73c561875e7631e771f37632417ae1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYIACcFAmE87VUJEDQLE8QBRhT9FiEERGhclbcw6RQS4OSJNAsTxAFG
FP0AAHVtAQDgNwvQJhZBWTa3jXsDrdNtH3DpduUbxl+r/J8fSmAD6gD/er1T
nyRQMTU++NEhwaiAsrLHnZG38YvLzVj/Iuer4QA=
=t2V2
-----END PGP SIGNATURE-----


--------3383fbcea5216ed70e0d6afcbab5c4b56f73c561875e7631e771f37632417ae1--