[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Konsole 1.4.2 krippled by default PATH variable
From:       Dave Feustel <dfeustel () verizon ! net>
Date:       2005-08-16 9:40:12
Message-ID: 200508160440.12774.dfeustel () verizon ! net
[Download RAW message or body]

This version of ksh does not work like the original ATT (and MKS) ksh.
Every instance of ATT Ksh executes .kshrc at startup whether it
is a login shell or not. .kshrc is used to set the shell environment
and define local functions.

On Monday 15 August 2005 22:26, Manuel Amador wrote:
> You could also add a conditional in your .bashrc to load your .profile
> if it has not been loaded.
> 
> something like PROFILE_LOADED
> 
> I think Mandrake used to do this.  Fedora does not.  Kind of annoying
> because /etc/profile never gets read.  but /etc/profile.d/*.sh do.
> 
> El sáb, 13-08-2005 a las 11:07 -0500, Dave Feustel escribió:
> > I solved part of my problem by adding -ls as an argument to the konsole command
> > in the applications section of the properties section of the konsole icon on 
> > the task panel. Works ok except I still have to do "set -o vi" manually.
> > 
> > On Saturday 13 August 2005 09:25, Michael Olbrich wrote:
> > > .profile is only executed by login shells. I don't know about .kshrc
> > > (bash always executes .bashrc). So what you want is a login shell:
> > > $ konsole --ls
> > > I'm not sure whether that works with ksh though.
> > > 
> > > michael
> > > 
> > > On Fri, Aug 12, 2005 at 10:05:57AM -0500, Dave Feustel wrote:
> > > > I just upgraded to KDE 3.3.2 from 3.2.2 and, while there
> > > > are many improvements, konsole is now *crippled* by the setting
> > > > of its default PATH. Konsole's default PATH does not have "." or /home/daf
> > > > included. As a result, the .profile and .kshrc files in my home 
> > > > directory do not get executed automatically. I have to manually 
> > > > execute the statement ". ./.profile; . ./.kshrc" to get the shell initialized
> > > > properly. And I have to do this for every shell I start.
> > > > 
> > > > Is there a fix for this problem?
> > > > 
> > > > Thanks,
> > > > Dave Feustel
> > > > _______________________________________________
> > > > kde-usability mailing list
> > > > kde-usability@kde.org
> > > > https://mail.kde.org/mailman/listinfo/kde-usability
> > > 
> > _______________________________________________
> > kde-usability mailing list
> > kde-usability@kde.org
> > https://mail.kde.org/mailman/listinfo/kde-usability
> -- 
> Manuel Amador                   <rudd-o@amautacorp.com>
> http://www.amautacorp.com/            +593 (4) 220-7010
> 
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread]