Is "uuencode filename" supposed to hang?

[Denys Vlasenko]

On Mon, Oct 10, 2011 at 6:48 PM, Rob Landley <rob at landley.net> wrote:
> Maybe I'm using it wrong.  When I go:
>
>  uuencode < file
>
> It complains I didn't give it a filename, but "uuencode filename" hangs
> without producing any output.

It waits for the input from stdin.

1.19.x has improved help text which hopefully makes
it clearer that one-parameter form does *not* specify input file,
but specifies filename to be printed in the encoded form:

$ busybox uuencode --help
busybox uuencode --help
BusyBox v1.19.2 (2011-09-12 21:02:22 CEST) multi-call binary.

Usage: uuencode [-m] [INFILE] STORED_FILENAME

$ echo "test" | busybox uuencode testfile


-- 
vda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testfile
Type: application/octet-stream
Size: 5 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20111010/8b84c02e/attachment.obj>