[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Pine screen painting?
That may just be the solution to the problem. You are having PT not interpret
the clear screen command, thus, keeping what had been presented. Later, you
can edit out those vt100 commands to regain the full text. I think that
is a decent approach when one is not able to command the host to do scrolling
vice screen repaints. Thanks for the tip.
Jack
In article <3vmtl9$55p@sulla.cyberstore.ca>, tsetse@trance.helix.net (tsetse) writes:
|> Louis Cornelio (lcornel@cello.gina.calstate.edu) wrote:
|>
|> : tsetse@trance.helix.net (tsetse) writes:
|> : > vt-100 screen control commands. incoming _raw_ characters can be captured
|> : > using the open-apple-c command.
|> :
|> : Exactly the problem; since Pine redraws the screen, what scrolls by is
|> : lost, unless scrollback capture is modified. Problem is, I tried to do it
|> : but it didn't work :-(
|> : ______________________________________________________________________
|>
|> puzzling. unless proterm behaves differently on a //gs and //e.
|> when i press (open-)apple-c, a dialog pops up named 'editor capture'.
|> it gives me the choice of 'copy raw incoming characters' or
|> 'copy entire processed lines'. it also lets me choose capture status bar
|> visible or not. last time i did this, i selected 'copy raw...' and
|> proterm saved the incoming character stream, vt100 codes and all. indeed,
|> the resulting file, once saved to disk, could be 'replayed' using the
|> 'file:emulate file' menu choice.
|> btw, i'm using proterm 3.1
|>
|> --
|> It is not possible that the possible and the | tsetse@helix.net
|> impossible are both possible - Babble 123 | +oO Vancouver.CA