Re: ProTerm 3.1 Upgrade

[yoshi@CSOS.ORST.EDU (Yoshi)]

Quinn Avery (quinn@Mountain.Net) wrote:
: Jeremy Chadwick (yoshi@CSOS.ORST.EDU) wrote:
: : 	The one thing which *REALLY* ticks me off about ProTERM v3.1 *AND*
: : 	did in v2.1 was the fact that the input-areas don't scroll when
: : 	you input more than however many chars it supports.

: An easy fix for this is to define a Macro for one of the mouse areas and
:  have it send your init string, then call that Macro from your startup
:  Macro.

	Sounds like a con-out on the part of a scrollable text window.
	Believe it or not, my reasoning behind my outlook is greed;
	ATZ takes longer to return "OK" than the full init code. (sighs)
	PT initializes about 4 or 5 seconds faster without using ATZ.
	I guess I could blame it on Supra and their "oh so wonderful"
	idea of switching over to the Rockwell chipset, but I won't.
	(buy USR! buy USR! Hehehe).

: One thing that bugs me is that vt100 windows put their discarded input
:  into scrollback, making the scrollback very difficult to read.  Using
:  my fave Mud client (vaportalk), I gotta clear the screen if I wanna
:  capture anything important, lest it be corrupted with subsequent typed
:  commands.

	Which client is this? I use tinyfugue, and I have no problems.

--
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Jeremy 'Yoshi' Chadwick           |Internet: yoshi@CSOS.ORST.EDU
Apprentice for Computer Science   |Phone: (503)753-2431
Outreach Services at Oregon State |IRC & UNiX Support
University                        |65c816 programmer (IIGS/SNES)