Date: Mon, 23 Nov 2015 07:31:07 +0800 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: "Michael B. Eichorn" <ike@michaeleichorn.com>, freebsd-stable Stable <freebsd-stable@FreeBSD.org> Subject: Re: su on 10.2: TERM: Undefined variable Message-ID: <20151123073107.49bca531@X220.alogt.com> In-Reply-To: <5651BD59.8070203@quip.cz> References: <5650642B.5030707@quip.cz> <1448138525.10590.18.camel@michaeleichorn.com> <5651A102.8050106@quip.cz> <5651BD59.8070203@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sun, 22 Nov 2015 14:04:25 +0100 Miroslav Lachman <000.fbsd@quip.cz> wrote: > > > > Miroslav Lachman > > The only workaround I found is adding > export TERM="" > at the top of the script. > this is a bit strange. TERM should be always define to tell the applications the capabilities of your terminal. When X is running, it is normally set to xterm, if nothing is available - or you do not know what is available - set it to vt100. Of course, the best would be to find out why it is not set on your machine. Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151123073107.49bca531>