| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | WTF is this? |
Paul, at 19:13 on Jun 02 1995, you wrote to Bill Grimsley... BG> No, as I said, I had to physically edit all control info from my BG> x-post as it was deleted the first time. I can assure you BG> unreservedly that the original had ALL control info 100% intact BG> (i.e. "@", "---", "PATH" and "SEEN-BY" were all there, one of the BG> intact origin lines _before_ the "@EOT:" kludge line). PE> You can have 15 million before it if you want, so long as there PE> is one after it. 15 million lines starting with "---" too. In PE> fact, as many ascii characters as you damn well like. Correct, according to the "Paul Edwards Book of FSC Kludges". It didn't occur to me that he must have _intentionally_ inserted his origin line within his SOT/EOT bracketed text, then Msged added the second one, as it's supposed to. BG> I didn't think that was possible with Msged 3.05 at all. PE> If you DON'T display seenbys, and you DO switch on SOT/EOT, then PE> Msged 3.05 will let you enter any printable ascii characters you want. True. I'd wondered why the imported message had been stripped of the control info I was trying to show you the first time, but I realise now that Msged saw the first EOT (the imported one) and deleted everything following that. PE> Are you sure the message actually violated FSC-XXXX.000? BG> I have no idea, that's purportedly your area of expertise. PE> It didn't appear to. BFN. Paul. No, it was just another Grimsleyan Brain Fart. [(C) RS 1994] Regards, Bill @EOT: --- Msgedsq/2 3.10 alpha* Origin: Save our native fauna. Kill a cat today! (3:711/934.18) SEEN-BY: 640/305 690/718 711/809 934 30163/9 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.