🚀 go-pugleaf

In <3888@phoenix.pub.uu.oz.au> markd@phoenix.pub.uu.oz.au (Mark Delany) writes:

>>Has anyone gotten the terminal emulations to work correctly? i would
>>ideally like a vt100 emulator, since adm31 doesn't recognize the PC
>>cursor keys. (Then again I'm no UNIX guru, and wouldn't know how to
>>fix it if it were easy..)

ADM31 does recognise the PC cursor keys, but since ADM31 uses control
characters rather than longer escape codes like VT100 does, some programs
may "eat" these control characters for other purposes, and render the
cursor keys ineffective.

>Changing the terminal type on the Unix server is pretty trivial (see
>server/uw_tty.c). You would not need to be a UNIX guru to do this.

>Changing the emulator on the PC end is not so easy as that is where the
>emulation actually occurs. You may need to be a PC guru to do this.

VT100 will be available in the next version of UW/PC on the PC end.  However,
it's not entirely necessary to hack the Unix server, though it would be
advantageous.  By adding a couple of lines like the following to your
.cshrc or .kshrc file, you can make the Unix side switch to the right
emulation on every newly-created window:

	case $TERM in
	  adm31|ansi) TERM=vt100 export TERM;;
	  *) ;;
	esac

(I don't know the csh equivalent).  I currently use something like this for
making it use ANSI rather than ADM31, because the UW server always creates
the first window using the ADM31 emulation.  I hope to fix this too by making
changes to the PC side to override ADM31 with the user's prefered terminal
type automatically.  Future versions of UW/PC may be distributed with patches
to the Unix server to add VT100 support.

Cheers,

Rhys.

+=====================+==================================+
||  Rhys Weatherley   |  The University of Queensland,  ||
||  rhys@cs.uq.oz.au  |  Australia.  G'day!!            ||
||       "I'm a FAQ nut - what's your problem?"         ||
+=====================+==================================+