[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-29 16:11:57
Message-ID: 200508291111.57469.dfeustel () verizon ! net
[Download RAW message or body]


The problems I was having with konsole somehow were all generated by
using xdm to start kde. I stopped using xdm for other reasons and all the 
problems with konsole disappeared. I'm happy now. :-)

Dave Feustel

On Wednesday 24 August 2005 17:49, Manuel Amador wrote:
> Dave, the solution is right there:
> 
> change your Xsession script to make it be run as a login shell
> 
> instead of
> #!/bin/bash
> 
> do 
> 
> #!/bin/bash --login
> 
> (yes, YES, I know you use ksh.  In this context, it is *not* important
> since the big problems you are experiencing are because of variable
> expansion, which bash does just fine.)
> 
> Basically, if you want your .profile to be interpreted when you log in
> to your XDM/KDM session, do that change to the Xsession script.
> 
> whether you use ksh or bash does not matter.
> 
> El mar, 23-08-2005 a las 08:22 -0500, Dave Feustel escribió:
> > On Tuesday 23 August 2005 08:08, James Richard Tyrer wrote:
> > > Dave Feustel wrote:
> > > > 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.
> > > 
> > > IIUC, that is the correct behavior for all shells.  That is the way it 
> > > is for Bash.  The script: ".bashrc" is run every time you open an 
> > > interactive shell session.
> > 
> > In KDE 3.2.3 ksh running in konsole would execute .profile automatically
> > also for new tabbed ksh shells. This is no longer the case in kde 3.2.3.
> > This change in behavior cripples tabbed shells since the default path
> > for the tabbed shells is so restricted. Although I like tabbed shells, I have
> > stopped using them since I have to manually initialize every one of them
> > with a . /home/daf/.profile before I can do anything useful. It's simpler
> > to just click on the shell icon to start a new login shell that *is* properly
> > initialized as a result of executing .profile. Note also that since .profile
> > is not executed by non-login shells, the environment is not initialized by
> > the script pointed to by the ENV variable. That means you get none of
> > your function definitions, should you  define them (as I do) to do useful
> >  things.
> > 
> > > However, there should be a file such as: ".profile" (don't know exactly 
> > > what it would be called for KSh -- Bash normally uses: ".bash_profile" 
> > > but it will use: ".profile" as a second choice) that is executed only at 
> > > login or in a login shell.
> > > 
> > > -- 
> > > JRT
> > > 
> > 
> -- 
> Manuel Amador                   <rudd-o@amautacorp.com>
> http://www.amautacorp.com/            +593 (4) 220-7010
> 

-- 
Tired of having to defend against Malware?
(You know: trojans, viruses, SPYWARE, ADWARE, 
KEYLOGGERS, rootkits, worms and popups) 
Then Switch to OpenBSD with a KDE desktop!!!
_______________________________________________
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]