The .bashrc shouldn't unset TERM but it is probably a better place to
put it since non-login terminals will pick up the variable there as well in
case it isn't exported from the parent process.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 17 Sep 2015, Maciej Sitarz wrote:
Date: Thu, 17 Sep 2015 11:14:22 +0200
From: Maciej Sitarz <[email protected]>
To: Robert Dinse <[email protected]>
Cc: [email protected]
Subject: Re: [X2Go-User] x2goclient connection fails with 'setterm: $TERM is
not defined'
W dniu 17.09.2015 o 11:06, Robert Dinse pisze:
In your .profile:
export TERM="vt102" or whatever terminal definition you prefer to
use, "ansi", etc.
The problem was that the /etc/profile.d configs are loaded before ~/.bashrc
and ~/.bash_profile.
According to man bash ~/.profile is loaded after them:
" When bash is invoked as an interactive login shell, or as a
non-interactive shell with the --login option, it first reads and executes
commands from the file /etc/profile, if that file exists. After reading
that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in
that order, and reads and executes commands from the first one that exists
and is readable. The --noprofile option may be used when the shell is
started to inhibit this behavior."
So adding TERM setting to /etc/profile should also help.
Thank you
--
Maciej Sitarz
_______________________________________________
x2go-user mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-user
