On Sun, 16 Oct 2005 13:57, Kevin O'Gorman wrote:
> I couldn't find it either. What bothers me is that in a Konsole, there's
> a Settings -> Configure Konsole -> Session -> $TERM
> setting that looks like it should override anything X does. I would
> expect that Konsole would be started, change the
Okay, I did that. The bug is #114511, found at
http://bugs.kde.org/show_bug.cgi?id=114511
++ kevinOn 10/16/05, Kevin O'Gorman <[EMAIL PROTECTED]> wrote:
I couldn't find it either. What bothers me is that in a Konsole, there's
a Settings -> Configure Konsole -> Session -> $TERM
setting that look
I couldn't find it either. What bothers me is that in a Konsole, there's
a Settings -> Configure Konsole -> Session -> $TERM
setting that looks like it should override anything X does. I would
expect that Konsole would be started, change the TERM environment
and start the indicated shell. This i
On Sun, 16 Oct 2005 03:06, Kevin O'Gorman wrote:
> I run Konsole for shell sessions, and things are going slightly wrong.
> I've tracked it down to the fact that although I've set the Konsole
> preferences to $TERM=linux, that variable is obdurately "xterm".
>
> When I put an echo in .bashrc or .ba
I run Konsole for shell sessions, and things are going slightly wrong.
I've tracked it down to the fact that although I've set the Konsole
preferences to $TERM=linux, that variable is obdurately "xterm".
When I put an echo in .bashrc or .bash_profile, it's already xterm.
How can I find the culpri
5 matches
Mail list logo