🚀 go-pugleaf

In article <8701272118.AA01023@yale-eli.YALE.ARPA>, ram-ashwin@YALE.ARPA.UUCP writes:
> I've been using uEmacs 3.7i for a while now and I never noticed this since OSS
> Pascal, 1stLatex, UUdecode, etc. all seemed to work fine with uEmacs'd files.
> However, Moshe's latest UUdecode dies when it sees CR-CR-LF.  It does decode
> freshly UUencoded files, and freshly Kermit'd files (but not Kermit'd and then
> uEmacs'd files) so my copy of his program does seem to be correct.  Anyone
> else run into this?
> Could someone please explain what's going on, and what the "correct"
> end-of-line terminator is?  And whether it really is uEmacs that's doing it
> (or is it Kermit (unlikely)? something else?)

Clearly, uEmacs is broken, not uudecode.  CR-CR-LF is 2 end of lines
folded together is the standard CPM format (i.e. one CR for each endofline and
only one LF).  SO uEmacs is putting blank lines between each line of the file
which of course terminates uudecode.
CORRECT end of line would only have CR or LF.  BUT CPM, TOS, MS-DOS etc want
CR-LF as end of line.
--j.a.tainter
> Thanx -- Ashwin Ram.
your welcome