From: CSBVAX::MRGATE!RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP 27-AUG-1988 17:07 To: ARISIA::EVERHART Subj: Re: LSE - writing multiple files w/o session termination Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Sat, 27 AUG 88 13:28:48 PDT Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Sat, 27 Aug 88 13:08:12 PDT Received: by ucbvax.Berkeley.EDU (5.59/1.31) id AA08841; Sat, 27 Aug 88 12:21:49 PDT Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-vax@kl.sri.com (info-vax@kl.sri.com) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 27 Aug 88 17:21:51 GMT From: bsu-cs!cfchiesa@iuvax.cs.indiana.edu (Christopher Chiesa) Organization: CS Dept, Ball St U, Muncie, Indiana Subject: Re: LSE - writing multiple files w/o session termination Message-Id: <3775@bsu-cs.UUCP> References: <5430@ut-emx.UUCP> Sender: info-vax-request@kl.sri.com To: info-vax@kl.sri.com In article <5430@ut-emx.UUCP>, tmca@ut-emx.UUCP (The Anarch) writes: > > > ... I'm running LSE and have 10 quadzillion files open ... and so I'll > have to write them before I leave ... I'm not the world's most sophisticated LSE user, but I can usually come up with a 'kludge' of some sort to get a job done... For saving all those open files; if by some chance you've done a SET OUTFILE (I believe it's something like that) for all buffers, then the EXIT command should automatically write all the files. (If you've been using GOTO FILE I think that automatically enables the SET OUTFILE for the new buffer(s) created...) The problem then, as I see it anyway, would simply be how to go about getting ALL those files back IN for your NEXT session. (I know, you don't want to terminate your session; but if someone crashes the system THAT will terminate your session for sure -- with "extreme prejudice," I might add. There's always LSE/RECOVER, to be sure, but you don't want to /RECOVER ten hours' worth of editor commands!) What I'd do in such a case - and this is by no means the ONLY, or BEST way, I'm sure - is: BEFORE EXITing: Do a SHOW BUFFERS ALL (or is it SHOW BUFFER * ?)(whatever), to display a list of all existing buffers (which, hopefully, will have the same names as the files you have open). Do a GOTO BUFFER $SHOW, which will allow you to treat the display you just saw as though it were a file to be edited. Do a WRITE SHOW_SAVE, which will save the list of buffers into a file. EXIT from LSE, go eat or whatever. When you return: Edit the SHOW_SAVE file to place a "goto file" in front of each file/buffer name, and remove everything else. When you're finished the file should con- tain only valid LSE "GOTO FILE" commands. Go into LSE, do a GOTO BUFFER/CREATE COMMAND and then a READ SHOW_SAVE. Do a DO/BUFFER=COMMAND. If you've done everything right this SHOULD treat the COMMAND buffer, containing the modified SHOW_SAVE file, as a set of LSE commands to be performed. Since you've filled that file, and buffer, with GOTO FILE commands, it should traipse around and yank in all the files named in SHOW_SAVE, which of course are the files you were working with in the last session. Note, the "real gurus" around here may have a shorter, more elegant, more dependable method. I'll be keeping my eyes open for it myself. It may in- volve one or more of the "Code Management System" utilities that DEC provides to keep track of what-module-goes-where-and-depends-on-what, which seems sort of in the same ballpark with keeping-track-of-what-files-I-was-using-and-get- ting-them-all-back-again. Til then, though, try what I've said and see if it helps. E-mail if you have difficulties. Chris Chiesa -- UUCP: !{iuvax,pur-ee,uunet}!bsu-cs!cfchiesa cfchiesa@bsu-cs.UUCP