Re: terminal weirdness?

[Ron DuFresne <dufresne () WINTERNET COM>]

understood, but, I thought the poster stated his TERM=vt100 and the result
he got back was a vt200 setting, yes?

Thanks,

Ron DuFresne


On Thu, 8 Mar 2001, Matt Zimmerman wrote:

> On Wed, Mar 07, 2001 at 10:40:07AM -0600, Blake Frantz wrote:
>
> > I telnet'd into port 1080, pressed enter, and got disconnected...fine.
> > But, after I got disconnected "VT102" was displayed at my command prompt.
> > I figured it was just 'misplaced output' or something from telnet, but
> > when I hit enter I got 'command not found'.  I don't understand where
> > VT102 came from, and why my shell interpreted it as valid input from
> > STDIN.   I checked env and term=vt100.  Just to do it, I
> >
> > strings `which telnet` | egrep -i "vt102"
> >
> > and nothing was found.  Could this be something sent from the proxy
> > server?  If so, can it be changed arbitrarily (rm -r *)?
>
> This is a feature.  When your terminal software receives an ENQ character, it
> will send back the name of your terminal (e.g., "vt100" or "xterm"), or
> whatever else it's been instructed to send back.  Try it (ENQ is ASCII 5).
>
> This is also the reason why receiving random binary data on a terminal will
> often cause the terminal name to be printed many times.
>
> In short, yes, this is caused by something sent from the proxy server (though
> said proxy server is probably broken), and yes, it can be changed, but only by
> the client terminal program, not by the ENQuiring side.  Probably the most you
> can do is frighten someone who doesn't understand what's happening
> (abracadabra, I will make you type "xterm"!).
>
> --
>  - mdz

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cutting the space budget really restores my faith in humanity.  It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
        ***testing, only testing, and damn good at it too!***

OK, so you're a Ph.D.  Just don't touch anything.