Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jun 1998 01:45:09 -0500 (CDT)
From:      Joel Ray Holveck <joelh@gnu.org>
To:        grog@lemis.com
Cc:        jkh@time.cdrom.com, sue@welearn.com.au, pechter@shell.monmouth.com, freebsd-hackers@FreeBSD.ORG
Subject:   Re: VT100 (was: PCVT's death)
Message-ID:  <199806240645.BAA01400@detlev.UUCP>
In-Reply-To: <19980624142512.C5023@freebie.lemis.com> (message from Greg Lehey on Wed, 24 Jun 1998 14:25:12 %2B0930)
References:  <19980624064036.I2801@freebie.lemis.com> <8949.898664000@time.cdrom.com> <19980624142512.C5023@freebie.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>>> That's a pity.  I'd guess that 95% of the non-hackers have never even
>>> heard of LINT.  Without having their heads stuck into it, I doubt
>> Most non-hackers have no idea what a vt100 terminal is either, or why
>> they'd even want to use one in this GUI-infested day and age.  No
>> problem, I guess. :)
> Well, one reason might be that most Microslop "telnet" abominations
> claim (without good reason) to emulate a VT100.
> Aside: Does anybody know one that works?

You mean a VT100 telnet client for Windows that works?  I'll list a
few in a second, but first I'll point out what I learned to handle
field circus calls.  I've found that if you take a few steps, the
client that comes with 95 can be marginally usable on most Unixes-- at
least, it handles emacs, nethack, and screen ok.

(1) Don't resize or move the window, or access the menus, unless you
don't expect to be receiving data during the operation.  The
temptation is great to resize to full screen during the MOTD, but if
data arrives while you're fiddling with this, then the telnet client
will be put in a bad state.  (It looks like a ring queue gets out of
sync, but I could be wrong.)

(2) Upon first logging in, type 'export TERM=vt100 ; stty rows 25' or
your shell's equivalent.  (On some machines, notably HP/UX systems,
the stty will fail.  On these machines, use 'export TERM=vt100
LINES=25' instead.)

(3) Resize the window to maximum size.  Just grab a corner and bring
it out until it don't go anymore.  (On 640x480 resolutions, this may
involve moving the window to the top of the screen first.)  I'll
occasionally think I have messed up a session, when all I had to do
was scroll down.  Now I just keep everything onscreen.

Some other concessions may have to be made for transmitted keys, but
the basic functionality is there.  (Emacs users: I recommend adding
  (global-set-key [?\C-c ?m] 'set-mark-command)
to your .emacs if your client won't send C-@.  This allows C-c m to set
the mark.)

Now, you also wanted a usable client.  I have used CRT, from Van Dyke
Software (http://www.vandyke.com/).  They have a very good
rlogin/telnet client, including separate settings for different
sessions, full VT-series emulation (with configurable color options),
and-- I just plain like this, for some reason-- it can use any Windows
fonts, or its internal VT100 fonts.  The web site has a 30-day demo
version availible, and the registration fee is light.

There are more options availible, including some no-charge
implementations, on Tucows (http://www.tucows.com/) and WinFiles
(http://www.winfiles.com/).  I am not aware of any that come with
source code, although I wouldn't be suprised to see it.  (I've been
meaning to write a pure console-mode telnet with VT100 support, but
haven't gotten around to it yet.  The only similar item I saw had one
minor bug in its newline handling that prevents redirection, which I
need.)

If you really want to go all-out, maybe you should use X.
Implementations for both 95 and NT availible.  There are a couple of
good no-charge ones, many commercial ones (some with demos, typically
30 minute or single machine).  I haven't seen any with source code.
Pointers availible.

Happy hacking,
joelh

-- 
Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806240645.BAA01400>