Jon Dowland wrote:
At 1146072858 past the epoch, John Stumbles wrote:
On my system .[x|X]session doesn't exist by default, so
kde (or whatever is chosen at the start-session menu) is
getting started by some other mechanism.
Yes, KDM is calling startkde which in turn calls kdeinit.
Thanks.
On 2006-04-26 16:41:47, Michael M. wrote:
> Felix C. Stegerman wrote:
> >
> >Since I use openbox + perlpanel + my_own_session_manager,
> >I just source my .bashrc in my .xinitrc.
>
> Sorry, Felix, could you explain what you mean my "my own session
> manager"? You mean something other than gdm, kd
At 1146072858 past the epoch, John Stumbles wrote:
> On my system .[x|X]session doesn't exist by default, so
> kde (or whatever is chosen at the start-session menu) is
> getting started by some other mechanism.
Yes, KDM is calling startkde which in turn calls kdeinit.
> At the 'Start new session'
Felix C. Stegerman wrote:
Since I use openbox + perlpanel + my_own_session_manager,
I just source my .bashrc in my .xinitrc.
Sorry, Felix, could you explain what you mean my "my own session
manager"? You mean something other than gdm, kdm, xdm or wdm?
--
Michael M. ++ Portland, OR ++ U
> Aha! that works! Thanks.
You're welcome.
> Is that documented somewhere?
> I've looked at http://www.kde.org/documentation/ especially
> http://www.kde.org/areas/sysadmin/, and http://docs.kde.org/
I found it out by reading (the comments in) /usr/bin/startkde,
but in unstable it's now documen
Jon Dowland wrote:
It depends entirely on which session manager is used or
which method of starting your session. If you create a
~/.xsession script which execs "startkde" you could specify
the PATH before that and have it inherited by startkde and
all subsequent processes. You then would need t
Felix C. Stegerman wrote:
Try renaming `setpath' to `setpath.sh'.
Aha! that works! Thanks.
Is that documented somewhere?
I've looked at http://www.kde.org/documentation/ especially
http://www.kde.org/areas/sysadmin/, and http://docs.kde.org/
Of course it only works for kde. That's good enou
On 2006-04-26 16:06:20, John Stumbles wrote:
> Felix C. Stegerman wrote:
>
> >I personally use .xsession / .xinitrc to start a custom X session and
> >add ~/bin to my $PATH in there.
> >To do the same with GNOME, you can edit ~/.gnomerc.
> >To do the same with KDE, you can create a new executable
On 2006-04-26 10:39:43, John Stumbles wrote:
> On kubuntu (and SuSE, IIRC) if I have a ~/bin directory it gets included
> in my $PATH but this doesn't happen under debian. (In all cases I'm
> using kde with kdm as my window manager.)
...
> I've googled www and usenet and searched debian lists but n
On Wed, 26 Apr 2006 12:41:36 +0100
Jon Dowland <[EMAIL PROTECTED]> wrote:
> At 1146047983 past the epoch, John Stumbles wrote:
> > I've googled www and usenet and searched debian lists but
> > not found an answer to the question of setting the
> > environment for my whole X session, not just for c
At 1146047983 past the epoch, John Stumbles wrote:
> I've googled www and usenet and searched debian lists but
> not found an answer to the question of setting the
> environment for my whole X session, not just for console
> session within X.
It depends entirely on which session manager is used or
On kubuntu (and SuSE, IIRC) if I have a ~/bin directory it gets included
in my $PATH but this doesn't happen under debian. (In all cases I'm
using kde with kdm as my window manager.)
The ~/.bash_profile of any new users I create has:
""
# include .b
12 matches
Mail list logo
