On Tuesday 14 November 2006 02:10, Bruce Sass wrote: > help:/konsole/sessions.html, point 4. clearly states: > "Enter a command just as you normally would if you opened a new shell > and were going to issue that command." Maybe this line has been thru the sales department, but I can also open new shells that don't read my .bashrc The line maybe could say "Enter a command as you normally would if you opened a new shell and were to issue that command. The command will be invoked with sh -c /command/" or maybe: "Enter a command as you normally would in a shell. This command will be executed instead of your shell" [snip irrellevant stuff describing konsoles use as a terminal, not as a program-runner] > Clearly, it would be a bug if bash was used on an "old-fashioned text > screen" and it didn't read .bashrc... so why is it OK for Konsole to > not make sure bash is started in a like manner? I have looked more into it. I cannot find any evidence that konsole actually invokes bash -c yourcommand, but instead I seem to suggest uses sh -c yourcommand (not that it changes anything in the big picture - exept /bin/sh never reads .bashrc) I would actually consider it a bug if I used a "old fashioned text screen" with sh and it read .bashrc pusling@pusling:~$ grep TESTV .bashrc export TESTVAR=brucesass pusling@pusling:~$ env | grep TESTV pusling@pusling:~$ sh $ env | grep TESTV $ /Sune -- How to open the firewall? You must get access on a laser head, so that from Excel you neither can ever disable the connection over the system to a sendmail to a space bar on the laser display, nor can debug a BIOS clock and from the control preferences menu within Photoshop NT you must save the clock and you cannot connect a level-7 TCP/IP directory of a folder on a USB front-end to load the pointer.
Description: PGP signature