Bug#397073: konsole: not reading ~/.bashrc

[Bruce Sass <bmsass@shaw.ca>]

On Mon November 13 2006 17:35, Sune Vuorela wrote:
> On Tuesday 14 November 2006 00:55, Bruce Sass wrote:
> > Perhaps the underlying bug is that konsole is not properly
> > identifying itself as a terminal.
>
> Maybe. xterm behaves same way.
>
> pusling@pusling:~$ echo TESTVAR=brucesass >> .bashrc
> ###press alt-f2 - type env > kdeenv
> pusling@pusling:~$ grep TESTVAR kdeenv
> ###press alt-f2 - type xterm -e "env > xtermenv"
> pusling@pusling:~$ grep TESTVAR xtermenv
> pusling@pusling:~$ grep SHELL xtermenv
> SHELL=/bin/bash
> XTERM_SHELL=/bin/bash
> pusling@pusling:~$
>
> so when having xterm invoke another program instead of bash also not
> read .bashrc - I find it correct for konsole to behave like xterm
> here.

Good point, but I am not doing `konsole -e gitfm' and that is not how 
sessions are supposed to work according to the Konsole docs.

<...>
> this says that .bashrc is _not_ read when doing bash -c

It turns out this is not relevent because sessions are supposed to work 
as "if you opened a new shell and were going to issue that command."

That is clearly not what is happenning (see my response to Clint's 
message"... for that reason alone this report should be forwarded 
upstream so they can determine if Konsole sessions are broken or 
behaviour has changed and the docs need to be updated. I have been 
using Konsole sessions for years and the lack of behaviour I am 
describing is recent.


- Bruce