Well there's "exactly what I want" and there's "good enough". Good enough may be piping your typescript through col -b and then through tr -d '\011' like so:
cat typescript | col -b | tr -d '\011' It might be a teeny bit better in conjunction with the knowledge that all those !@#$% colors in your ls output can be disabled by doing "ls --color=never" instead of just "ls". An accurate log of a session should include the control codes, but if what you absolutely have to have is a cooked, text-only version as would be produced by xterm's original logging option, then (as someone else already said i think) you can recompile xterm. :-( Wonder why they chopped that out... -----Original Message----- From: dbrett [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 27, 2002 6:15 AM To: Eric Wood Cc: [EMAIL PROTECTED] Subject: Re: Replacement for telnet Hi Eric This will work, the problem is trying to identify all the escape sequences. Try running script then run 'ls' and then telnet to another device. You will see a number of different escape sequences. david On Wed, 27 Mar 2002, Eric Wood wrote: > > I have not found an easy method of > > removing the characters. > > try > > sed -e "s/^M//" filename > newfilename > > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
