It's more likely to be a problem with your shell environment than xterm.
--
TERM environment variable not set.
https://bugs.launchpad.net/bugs/652160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I don't see the shell mentioned (assuming bash). It's not a problem with the
terminal database,
otherwise you'd not succeed in using the exported $TERM. So I'm assuming some
scripting
error in the shell's initialization is clearing the variable.
--
TERM environment variable not set.
https://b
yOn Fri, 1 Oct 2010, Daniel Holm wrote:
> Yes. It is bash. What do you want me to do?
I'm curious if there's something in its initialization scripts which is
doing an "unset" on TERM, or exporting it to some odd value.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
On Fri, 17 Sep 2010, Schplurtz le déboulonné wrote:
> Hello,
>
> The bug is still there in Lucid.
>
> After reading Thomas Dickey's comment, I think there is no need to mark
> the bug as new. Am I right ?
right - it's a longstanding bug. iirc, mawk is reading the token in a
context where it's n
There's no test-program which demonstrates the problem,
so there is no possibility to analyze these comments.
By the way, Ubuntu provides by itself no solutions or improvements of
any type for ncurses.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
301 - 305 of 305 matches
Mail list logo
