Hi,
I installed Bash over the free conda channel (version Bash 4.3.48). This version seems to have a problem with its terminal config.
The bash version don't read the TERM env correctly.
For example:
$> export TERM=xterm
$> export TERMINFO=/usr/share/lib/terminfo
$> echo $TERM
xterm
$> clear
'/u/userid': unknown terminal type.
echo $TERM
xterm
I would guess this bash version reads the homedir env instead of term.
Rolling back to the previous Version fixes the problem.
Kind regards,
Björn
------------------------------
Björn Schanz
Sysprog
R + V Allgemeine Versicherung AG
Wiesbaden Germany
------------------------------
+1- Rocketeer
- 110 replies
Hi,
I installed Bash over the free conda channel (version Bash 4.3.48). This version seems to have a problem with its terminal config.
The bash version don't read the TERM env correctly.
For example:
$> export TERM=xterm
$> export TERMINFO=/usr/share/lib/terminfo
$> echo $TERM
xterm
$> clear
'/u/userid': unknown terminal type.
echo $TERM
xterm
I would guess this bash version reads the homedir env instead of term.
Rolling back to the previous Version fixes the problem.
Kind regards,
Björn
------------------------------
Björn Schanz
Sysprog
R + V Allgemeine Versicherung AG
Wiesbaden Germany
------------------------------
I installed Bash over the free conda channel (version Bash 4.3.48). This version seems to have a problem with its terminal config.
The bash version don't read the TERM env correctly.
For example:
$> export TERM=xterm
$> export TERMINFO=/usr/share/lib/terminfo
$> echo $TERM
xterm
$> clear
'/u/userid': unknown terminal type.
echo $TERM
xterm
I would guess this bash version reads the homedir env instead of term.
Rolling back to the previous Version fixes the problem.
Kind regards,
Björn
------------------------------
Björn Schanz
Sysprog
R + V Allgemeine Versicherung AG
Wiesbaden Germany
------------------------------
It's actually an issue with the 'clear' command rather than with bash itself. Most probably you have the ncurses package in your environment (it's installed as a part of Rocket AppDev for Z); 'clear' is a part of that package. We've already fixed this issue in ncurses, but at the moment the fix is only available to customers on support contract. The free channel still contains an old build of ncurses, and is going to be updated in March 2022.
Meanwhile, you can use USS's built-in 'clear' (located in /bin) as a workaround. There are a couple of ways to do this:
a) add the following line to your profile:
alias clear='/bin/clear'
- or -
b) manually delete the file named 'clear' from the bin directory in your environment.
Regards,
Vladimir
------------------------------
Vladimir Ein
Rocket Internal - All Brands
------------------------------
Hi Björn,
It's actually an issue with the 'clear' command rather than with bash itself. Most probably you have the ncurses package in your environment (it's installed as a part of Rocket AppDev for Z); 'clear' is a part of that package. We've already fixed this issue in ncurses, but at the moment the fix is only available to customers on support contract. The free channel still contains an old build of ncurses, and is going to be updated in March 2022.
Meanwhile, you can use USS's built-in 'clear' (located in /bin) as a workaround. There are a couple of ways to do this:
a) add the following line to your profile:
alias clear='/bin/clear'
- or -
b) manually delete the file named 'clear' from the bin directory in your environment.
Regards,
Vladimir
------------------------------
Vladimir Ein
Rocket Internal - All Brands
------------------------------
It's actually an issue with the 'clear' command rather than with bash itself. Most probably you have the ncurses package in your environment (it's installed as a part of Rocket AppDev for Z); 'clear' is a part of that package. We've already fixed this issue in ncurses, but at the moment the fix is only available to customers on support contract. The free channel still contains an old build of ncurses, and is going to be updated in March 2022.
Meanwhile, you can use USS's built-in 'clear' (located in /bin) as a workaround. There are a couple of ways to do this:
a) add the following line to your profile:
alias clear='/bin/clear'
- or -
b) manually delete the file named 'clear' from the bin directory in your environment.
Regards,
Vladimir
------------------------------
Vladimir Ein
Rocket Internal - All Brands
------------------------------
this makes sense to me. Using the build-in version of clear fixes the problem. Thank you.
Kind regards,
Björn
------------------------------
Björn Schanz
Sysprog
R + V Allgemeine Versicherung AG
Wiesbaden Germany
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
