On Mon November 13 2006 16:13, Sune Vuorela wrote: > On Monday 13 November 2006 23:38, Bruce Sass wrote: > > You seem to be doing a lot of guessing... :-/ > > which is why I am sending a copy to your Application Manager. > > Thank you. You are most welcome to show my application manager that I > do a hard work on the kde bugs.
Or how you tackle reports about programs for which you have limited knowledge---sessions are a key feature of konsole, they get their own tab in the config dialog, yet you were unaware of them and blindly went ahead tagging the report as unreproducible. > > Kurt, please have a look at: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073 > > > > > If you read the bash manpage, it says that bash only read .bashrc > > > when invoked interactively. > > > > Since when is a Konsole session not interactive? > > bash is not interactive when not connected to a terminal. This is > bash behaviour, not konsole behaviour. > > From the bash manpage: > > An interactive shell is one started without non-option > arguments and without the -c option whose standard input and error > are both connected to terminals (as determined by isatty(3)), > or one started with the -i option. PS1 is set and $- includes > i if bash is interactive, allowing a shell script or a startup file > to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. > > > and this is how bash is supposed to work - so this is not a bug > > > neither in konsole or in bash. > > > > You are wrong. > > Please point me where. Konsole should behave like any other x-terminal (which are interactive), "sessions" are like "bash -c somecommand" (you have admitted as much)... both point to .bashrc being read. > > .bashrc is not some random configuration file, and a program should > > not be required to read a shell's profile or runtime configuration > > files! > > .bashrc is just a random canfiguration file. Just try ask any zsh > user. What does zsh have to do with Konsole putting "SHELL=/bin/bash" in the environment? > > I think you should remove the "wontfix" tags and get some help from > > a knowledgeable DD, or send it upstream. > > I actually have discussed this with several knowledgeable DDs and > they agree with me. Then you should send it upstream because "sessions" are crippled... it should not matter if one starts a "shell" session then types in a command vs. uses a pre-defined session to start the command. > Please stop being abusive. How have I been abusive? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]