home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.vms:21801 vmsnet.sources.d:786
- Path: sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms,vmsnet.sources.d
- Subject: Re: Utility-Log session escape sequence filter
- Date: 23 Jan 1993 00:47:41 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 29
- Distribution: world
- Message-ID: <1jq4jdINNhrv@gap.caltech.edu>
- References: <1993Jan22.171051.581@dymaxion.ns.ca>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1993Jan22.171051.581@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
- =Freebie utility follows.
- =
- =Here's what should be a fairly common problem. Many packages log
- =sessions. Few of them filter ANSI escape sequences so that the logs
- =may be printed. Non-DEC printers are particularly awful at printing
- =such logs. Many non-DEC printers do unpredictable things with the
- =escape sequences. Some simply refuse to print further until someone
- =manually clears each invalid sequence using front-panel buttons.
- =Manually editing the logs is cumbersome.
- =
- =I'd like to see how people handle this situation. I am aware of PHOTO
- =and its control-sequence filtering capability, but PHOTO cannot be
- =used in all situations (e.g. I don't believe it handles SET HOST
- =sessions).
-
- Well, since I don't run PHOTO here, this is just a guess, but couldn't you:
- 1) SET HOST/LOG
- 2) After you've returned to the local system, use PHOTO and the
- command TYPE/NOPAGE SETHOST.LOG to filter out the control sequences
- in SETHOST.LOG?
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-