Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!GRIN2.BITNET!MCGUIRE From: MCGUIRE@GRIN2.BITNET.UUCP Newsgroups: comp.os.vms Subject: RE: shar for VMS Message-ID: <8706200546.AA09630@ucbvax.Berkeley.EDU> Date: Fri, 19-Jun-87 13:38:00 EDT Article-I.D.: ucbvax.8706200546.AA09630 Posted: Fri Jun 19 13:38:00 1987 Date-Received: Sun, 21-Jun-87 04:27:56 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 46 X> Date: 15 Jun 87 03:42:50 GMT X> From: Michael Bednarek X> Subject: Re: shar for VMS X> X> I didn't experience any troubles in this respect with mail/news items. X> Long lines were always intact, and source code should not be sensitive to X> trailing spaces/tabs whatever. X> However, leading spaces/tabs seemed to be eaten. That's why the leading X X> is used. X XItems sent using GMAIL via Jnet are a problem. Lines longer than 80 Xcolumns are wrapped. That means that most VMS sites on BITNET will wrap Xlong lines. X XYou could wrap yourself at 80, and put the records back together at the Xother end. What you might want to do is put the byte-count at the Xbeginning of the record instead of an `X'. The byte-count would tell you Xat the receiving end whether there is a wrapped line, and also would Xeliminate any problems with space pads. X XThe difficulty with records that are padded is that the checksums fail. X X> Speaking of which, does anybody out there know a method to use EDIT from X> a procedure to a) insert an X as the first character in each line and X> b) to remove it? X XPresumably you're talking about EDT. Try the following line mode command. XYou put it into an INI file, or EDT/COMMAND=SYS$INPUT and put it in the Xcommand procedure, or something on that order. X X CHANGE; ER -L 32000(88ASC -2L) X XThis arcane statement does the following: X X 1. Moves to end of buffer X 2. Moves to beginning of last record X 3. Repeats the following steps until failure: X 3.1. Inserts an X (ASCII 88) as the first character of the record X 3.2. Backs up to the beginning of the record, and again to the X beginning of the previous record. If there is no previous X record, the statement will fail, ending the loop. X XI haven't tested it as part of a command procedure. However, you can see Xthat I tested it interactively on this message :-) X XEd