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

2006-11-16 Thread Kurt Roeckx
On Mon, Nov 13, 2006 at 03:38:34PM -0700, Bruce Sass wrote: > > Kurt, please have a look at: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073 Dear Mr. Sass, Thank you for bringing this to my attention. But I don't see why you need to contact me for this. The package is group maintaine

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

2006-11-14 Thread Kevin Krammer
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." > > However, that is not what is happening as the attached diff of GIT > sta

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 20:00, Sune Vuorela wrote: > 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 lin

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

2006-11-13 Thread Sune Vuorela
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

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 18:34, you wrote: > > That is not correct; Konsole is for interactive use so -i should > > not be necessary. Furthermore... > > You are misunderstanding the bash man page. The '-c' makes bash > non-interactive. I understand that, it turns out I was wrong in assuming a Kons

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 18:02, Sune Vuorela wrote: > On Tuesday 14 November 2006 01:35, Sune Vuorela wrote: > > [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass >> .bashrc > > woops. Typo here - it should have been echo export TESTVAR=brucesass So, does that change the outcome? I don't see it as rele

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

2006-11-13 Thread Clint Adams
> That is not correct; Konsole is for interactive use so -i should not be > necessary. Furthermore... You are misunderstanding the bash man page. The '-c' makes bash non-interactive. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT

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

2006-11-13 Thread Bruce Sass
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. > > [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass >> .bashr

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 17:27, Clint Adams wrote: > > >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.

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

2006-11-13 Thread Clint Adams
> >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 inter

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

2006-11-13 Thread Bruce Sass
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 > d

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 14:50, Sune Vuorela wrote: > #first step on unversioned close: > tag 397073 +wontfix > thanks > > On Monday 13 November 2006 13:20, Bruce Sass wrote: > > That makes little sense to me---Konsole is a fancy x-terminal and > > should be doing the equivalent of "bash -c someprog

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

2006-11-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > #first step on unversioned close: > tag 397073 +wontfix Bug#397073: konsole: not reading ~/.bashrc There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracki

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

2006-11-13 Thread Bruce Sass
On Mon November 13 2006 03:11, Sune Vuorela wrote: > On Monday 13 November 2006 05:33, Bruce Sass wrote: > > > Is it something for konsole to run _instead_ of bash? or? > > > > hmmm, ya, sure... > > hmm... so you expect konsole to read conffiles for bash when it is > actually running another shell/

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

2006-11-12 Thread Bruce Sass
> hmm.. > > What is a "session program"? A program started via the "Session" menu, maybe I should be calling them Konsole Applications. > How do I set up a session program? - start konsole - select "Configure Konsole" from the "Settings" menu - select the "Session" tab - put a descriptive name

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

2006-11-12 Thread Bruce Sass
Hi, A konsole shell is fine, but session programs are not. I have a session which starts GNU Interactive Tools (apt-get install git) using the command "gitfm". The output of "env" from within that session is... - KDE_FULL_SESSION=true GS_LIB=/home/bsass/.fonts DM_CONTROL=/var/run/xdmctl GIT

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

2006-11-04 Thread Bruce Sass
Package: konsole Version: 4:3.5.5a.dfsg.1-1 Severity: important When starting session programs ~/.bashrc is not being read, which results in some programs not operating as configured. For example... My ~/.bashrc contains: eval `lesspipe` export GIT_PAGER=less which tells "gitfm" to use less as