[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: using screen logs

From: Will Stevenson
Subject: Re: using screen logs
Date: Fri, 30 Jan 2009 12:30:54 -0500
User-agent: Thunderbird (Windows/20081209)

Hi Jae,

I spent several hours trying to tackle this same issue. I wanted to share what I found out. I found 2 programs that do a pretty good job in removing the escape codes:

1.  Ansifilter:
2.  Ansi2txt:

Ansi2txt does a slightly better job (in my opinion) than Ansifilter. After running these programs, the output files were human-readable. Try them both out and let us know what you think.

>On Fri, Jan 30, 2009 at 5:52 AM, Jae Norment <address@hidden <mailto:address@hidden>> wrote:
>I use screen to log sessions where I patch Debian servers.  Screen
>captures ANSI control codes (like positioning and color changes), which
>is probably appropriate, however, I want a version of the logs without
>those codes so that I can open it in a text editor.  I've been told that
>a little perl could help, been directed to 'script', both of which don't
>seem to do the trick that I want.  For the perl solution, I need to know
>too much about the ANSI codes that I want to replace.  Script just
>dumps... there doesn't seem to be a good way to capture without the
>Screen is a widely used application, and my use to generate logs of my
>sessions has got to be a fairly popular function of screen... so what is
>everyone else using to make the logs human readable?  ( Ideally, I'd
>like something that will reformat the log either to a file or to a pipe.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]