X Applications at start up

[mbertrand]

I was putting my app at the end of .xsession for auto start and was told that it should go in '.x.d' So I moved it there.
I have 'xvtouch' starting in .xsession (this is for our touch screen). I was wondering is all of my .xsession is processed before
.x.d  ?

[tinypoodle]

You were told "~/.X.d/"
Not the same!

[gerald_clark]

Please cat .xsession.
You will see how the scripts are run, and the proper directory name.
The reason for putting them in .X.d is so you don;t lose them if .xsession is updated.

[mbertrand]

Oops I did a typo I meant "~/.X.d/".
Thanks for the advice.

[Pseudoman]

Did you place a script there in ~/.X.d/ to launch the application?
For example, if we had an X program named foo:
~/.X.d/foo

Code: [Select]

# !/bin/sh
# script to launch foo
foo &

Something like that, but it depends on what you need to do. I launch flit on start-up this way.

[hiro]

Way to go sure noone will ever understand .xsession
why can't you guys simply delete .X.d again?

[gerald_clark]

Hiro, mbertrand stated that he was editing.xsession.
I therefor believe he can read it and follow the simple script.

This is a tool kit. Don't assume it is too difficult for everyone else to understand.

[coreplayer2]

The reason for putting them in .X.d is so you don't lose them if .xsession is updated.

Thanks for this, I often wondered the reason why..

[hiro]

I never lose my .xsession. If there is an important change I can merge manually. But I can't argue agains power users who have to change their .xsession every week...