Tiny Core Base > TCB Talk
Inconsequent TERM variable setting
bmarkus:
Environment variable TERM is set to 'rxvt' for programs in aterm, while it is set to 'linux' for programs started with exec on WBAR or in applications menu of TC. It means that programs get different TERM environment variable depending on running aterm or lxterminal (or other terminal emulators). It is the reason why for example midnight-commander behaves differently in certain cases. Changing TERM manually to 'rxvt' fix such problems.
Would appreciate TERM=rxvt in all cases provided by the base.
tinypoodle:
if
--- Quote ---TERM=rxvt in all cases provided by the base
--- End quote ---
would all applications still work to satisfaction on the console (VT)?
bmarkus:
--- Quote from: tinypoodle on September 13, 2010, 01:06:56 AM ---if
--- Quote ---TERM=rxvt in all cases provided by the base
--- End quote ---
would all applications still work to satisfaction on the console (VT)?
--- End quote ---
For sure nobody can make a statement that all apllications will work... However 'rxvt' is the defaut setting for all console applications, so there are no change. urxvt is an rxvt emulator, so it is ok. Most of the other terminal emulators, like lxterminal, Terminal, etc. are only GUI's to the vte engine. vte is configured for also rxvt, see /usr/local/share/vte/termcap. If it is running with TERM=linux it is causing false operation of keyboard, etc.
Anyhow, current setting is inconsequent and the best way is to cure this. Then deal with remaining problems if there is any.
tinypoodle:
Thanks for the explanation! :)
curaga:
Maybe in .xsession, so that the linux console stays as is.
Navigation
[0] Message Index
[#] Next page
Go to full version