home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!SIVM.BITNET!NASSH100
- Message-ID: <NOTABENE%92121404173790@TAUNIVM>
- Date: Sun, 13 Dec 92 21:08:19 EST
- Sender: Nota Bene List <NOTABENE@TAUNIVM.BITNET>
- Comments: Converted from PROFS to RFC822 format by PUMP V2.2
- From: Allan Needell <NASSH100@SIVM.BITNET>
- Subject: Re: an xxdecode trick
- Newsgroups: bit.listserv.notabene
- In-Reply-To: note of 12/13/92 15:07
- Lines: 26
-
- From: Allan Needell
-
- Paul,
-
- I did mean following. The extra spaces appear at the beginning of each line,
- not the end. To remove them and make the downloaded email file suitable for
- xxdecoding, I copy a carriage return character and the following space (which
- is on the next screen line) to the command line. I get a double ascii combo
- (ascii 10 and a music symbol or some such) and a space. After the space I
- insert a separator and copy another cr combo and a separator without the
- space. I realize this is probably all unecessary and simply removing the
- spaces will suffice. But I tried that once and it didn't seem to work, while
- this longer procedure always does.
-
- When I execute the change routine, the whole xxcode block moves one space to
- the left (i.e. to the margin). I store the file, shell to dos and run uudecode
- on the file (which I have given the .xxe extension).
-
- I will send for the uuencode upgrade. I doubt it will work on my downloaded
- xxencoded email files, however, without this editing. I'll let you know if I
- am wrong.
-
- Allan Needell
- National Air & Space Museum
- Smithsonian Institution
- Washington, DC 20560 (BITNET: NASSH100@SIVM)
-