v130 doesn't parse rc file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. set variables in rc file (such as nitrogen --restore &)
2. startx
3. no background (or dzen or xscreensaver)

What is the expected output? What do you see instead?
I expected the services I set up in the euclidrc file to be started, instead I 
had to open a terminal and run all the applications at boot

What version of the product are you using? On what operating system?
v130 in Arch from the PKGBUILD

Please provide any additional information below.
This just started happening when I switched from 124 to 130.

Original issue reported on code.google.com by benjamin...@gmail.com on 18 Jul 2010 at 5:01

[GoogleCodeExporter]

also, M+r gives a "error spawning: /home/ben/.config/euclid-wm/euclidrc   
ERRNO: 14" which I'm sure is related.

BKL

Original comment by benjamin...@gmail.com on 18 Jul 2010 at 5:05

[GoogleCodeExporter]

The ERRNO 14 is not *directly* related (there might be a relation, but I get 
the ERRNO: 14 even though my rc starts fine at startup). This is just to say, 
they can be separated in fact, although the root causes may be related. I'm 
looking into what causes this. 

Will your rc run by itself? If you type /home/ben/.config/euclid-wm/euclidrc 
does everything start? 

Did you modify it at all during this period? Or did you install a new one by 
hand? Did you start euclid with star-euclid? Did the original get 
overwritten/reinstalled during install or the first startup? 

It sounds to me like something happened to the rc file because a) my rc is 
running (at startup), b) I've gone over the changes between 124 and 130 and 
they are mostly cosmetic (whitespace, comments, etc). Nothing that should be at 
all related to spawning the rc. So it looks like either something is wrong with 
the install/firstrun stuff, or like something else happened at or about the 
same time that made the rc unrunnable. 

Original comment by wmd...@gmail.com on 18 Jul 2010 at 1:24

[GoogleCodeExporter]

Running euclidrc by itself works.

I copied the new rc file from /usr/share/euclid-wm (with the minor changes you 
made to it) to my ~/.config/euclid-wm folder and added the changes that I use 
(nitrogen, xscreensaver, conky|dzen2) which is how I have been modifying it 
previously. Pretty much unneccessary since you just changed the comments and 
not any scripting language.

I'll pastebin my rc so you can check it out
http://pastebin.com/cXWGWE0d

Maybe it was a copy problem, I'm not sure? I'll try a fresh install and see 
what's up.

Original comment by benjamin...@gmail.com on 18 Jul 2010 at 1:35

[GoogleCodeExporter]

And I am exec euclid-wm in my .xinitrc. I'll switch it over to start-euclid and 
let you know how it goes.

Original comment by benjamin...@gmail.com on 18 Jul 2010 at 1:38

[GoogleCodeExporter]

Okay I moved the comments between my lines in the rc (just for cleanliness), 
and started euclid with 'exec start-euclid' and still no dice.

When my desktop came up I did ".config/euclid-wm/euclidrc" in dmenu and all of 
my configurations loaded just fine. Not sure what's going on.

Original comment by benjamin...@gmail.com on 18 Jul 2010 at 1:41

[GoogleCodeExporter]

Both issues should be fixed in r131. 
I've gone back to using system(); exec has just been a PIA from the start, and 
the benefits are too few for the frustration and bugginess. I'm sure it was 
just me doing something stupid, but I hit a wall with it, so if anyone wants to 
go back and do exec right, have at it. 'Till then it should work as expected. 
Hopefully we are back on schedule for rc1. 

Original comment by wmd...@gmail.com on 18 Jul 2010 at 2:37

• Changed state: Fixed