Subject: RE: Shell problem with 1.6
To: None <netbsd-help@netbsd.org>
From: Marechal, Laurent <lmarechal@rational.com>
List: netbsd-help
Date: 09/27/2002 19:17:45
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C26649.CB79FB50
Content-Type: text/plain;
charset="iso-8859-7"
Thanks for you help.
The strange think is that my term entry was set to
TERM=xterm
since the begining as with 1.5.3
But after logout/login without changing anything) the error is gone.
Thanks you
Laurent\
-----Original Message-----
From: Giorgos Keramidas [mailto:keramida@FreeBSD.org]
Sent: Friday, September 27, 2002 6:41 PM
To: Marechal, Laurent; netbsd-help@netbsd.org
Subject: Re: Shell problem with 1.6
RE: Shell problem with 1.6Marechal, Laurent wrote:
:
: Thanks for your answers,
: I changed the shell to sh (vipw made the trick).
:
: As for the ESC char, the 'set -E' doesn't work in csh
: (set: variable name must begin with a letter)
Obviously. The "set -E" trick is sh(1) specific.
: and fail in sh (No entry for terminal type network,
: using dumb terminal setting). Under sh, the 'set -E'
: fail with this error and then all the terminal app
: (ie pico, vi...) just fail...
That's a different type of beast. You have TERM=network
in your environment, which sh(1) doesn't know about
(it obviously fails to locate the proper termcap entry).
You can get around this by setting TERM to something
that sh(1) knows about. Try the following in sh(1):
$ TERM=vt100
$ export TERM
$ set -E
Giorgos.
------_=_NextPart_001_01C26649.CB79FB50
Content-Type: text/html;
charset="iso-8859-7"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-7">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: Shell problem with 1.6</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks for you help.</FONT>
</P>
<P><FONT SIZE=2>The strange think is that my term entry was set to </FONT>
<BR> <FONT SIZE=2>TERM=xterm</FONT>
<BR><FONT SIZE=2>since the begining as with 1.5.3</FONT>
</P>
<P><FONT SIZE=2>But after logout/login without changing anything) the error is gone.</FONT>
</P>
<P><FONT SIZE=2>Thanks you</FONT>
</P>
<P><FONT SIZE=2>Laurent\</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Giorgos Keramidas [<A HREF="mailto:keramida@FreeBSD.org">mailto:keramida@FreeBSD.org</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday, September 27, 2002 6:41 PM</FONT>
<BR><FONT SIZE=2>To: Marechal, Laurent; netbsd-help@netbsd.org</FONT>
<BR><FONT SIZE=2>Subject: Re: Shell problem with 1.6</FONT>
</P>
<BR>
<P><FONT SIZE=2>RE: Shell problem with 1.6Marechal, Laurent wrote:</FONT>
<BR><FONT SIZE=2>:</FONT>
<BR><FONT SIZE=2>: Thanks for your answers,</FONT>
<BR><FONT SIZE=2>: I changed the shell to sh (vipw made the trick).</FONT>
<BR><FONT SIZE=2>:</FONT>
<BR><FONT SIZE=2>: As for the ESC char, the 'set -E' doesn't work in csh</FONT>
<BR><FONT SIZE=2>: (set: variable name must begin with a letter)</FONT>
</P>
<P><FONT SIZE=2>Obviously. The "set -E" trick is sh(1) specific.</FONT>
</P>
<P><FONT SIZE=2>: and fail in sh (No entry for terminal type network,</FONT>
<BR><FONT SIZE=2>: using dumb terminal setting). Under sh, the 'set -E'</FONT>
<BR><FONT SIZE=2>: fail with this error and then all the terminal app</FONT>
<BR><FONT SIZE=2>: (ie pico, vi...) just fail...</FONT>
</P>
<P><FONT SIZE=2>That's a different type of beast. You have TERM=network</FONT>
<BR><FONT SIZE=2>in your environment, which sh(1) doesn't know about</FONT>
<BR><FONT SIZE=2>(it obviously fails to locate the proper termcap entry).</FONT>
<BR><FONT SIZE=2>You can get around this by setting TERM to something</FONT>
<BR><FONT SIZE=2>that sh(1) knows about. Try the following in sh(1):</FONT>
</P>
<P><FONT SIZE=2> $ TERM=vt100</FONT>
<BR><FONT SIZE=2> $ export TERM</FONT>
<BR><FONT SIZE=2> $ set -E</FONT>
</P>
<P><FONT SIZE=2>Giorgos.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C26649.CB79FB50--