On Monday, 6 de June de 2011 17:20:57 Robin Burchell wrote: > Hi, > > I've been doing some cursory kicking of the tires of the (very recently > released) meego-terminal > (https://gitorious.org/meego-terminal/meego-terminal/), and one thing > that came up pretty quick when I tried to run top was that TERM wasn't set. > > Who's responsibility is it to have this set? uxlaunch seems one > candidate, but I don't know if that's correct?
The graphical terminal application itself needs to set it to the value of what
it supports.
Or do you mean in a virtual console? If you mean that, it's the kernel that
sets it:
init/main.c:const char * envp_init[MAX_INIT_ENVS+2] = { "HOME=/",
"TERM=linux", NULL, };
So the question turns from "what failed to set it" to "what unset it"?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
