GoogleCodeExporter
commented
9 years ago First, as to not parsing the file:
It is parsing my config files. So I suspect there is something site-specific
going on.
In your message to the mailing list, you mentioned a Ctrl + Alt + enter
binding; right now euclid will choke on that. Euclid currently supports exactly
one mod key (mod1 OR mod2 OR . . . ), and that modkey + shift; so there is no
parsable way to tell it to use M1 + M2 + some key.
BTW, assuming the conf file is in the right place, try piping euclid-wm into a
file when you start it. You should see if it hits errors when it parses the
config file. Just for clarity, the right place is something like
~/.config/euclid-wm/euclid-wm.conf depending on the value of XDG_CONFIG_HOME .
Second, I'm assuming when you tried to install the conf files, you ran "make
install_conf" as a normal user. Again, I just tested it, and on my system this
works (as I've said before, however, I strongly dislike this system and am
planning to change it). I suspect that the problem with the configs not loading
may be that you made a typo when you manually installed the config files. But
that is just a guess.
The reason for the multiple definitions in the makefile is that according to
the spec (
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html ),
desktop programs should keep their configs in $XDG_CONFIG_HOME if it is
defined. Otherwise, they should use $HOME/.config (which typically is what
XDG_CONFIG_HOME is defined as) Creating the euclid-wm directory within that
just seemed neat (in the sense of clean and uncluttered). And nothing that
euclid creates should be a true dotfile, as in they should not have a "." in
front of them. (Maybe this was the typo in the manual install?)
Again from your mailing list message:
"Further, the -D on the install line isn't creating the full path since
$CONFDIR envokes a different variable within it. It's like a double
macro."
I can't reproduce it, the variables are getting defined fine on my end. I don't
think variables in makefiles bahave like macros.
All this said I might well end trying to use XDG_CONFIG_HOME. On a practical
level I don't really see this standard as having much value, in other words, I
agree that there probably is no reason not to put it all in $HOME/.euclid-wm .
But on the otherhand, I've already coded it and I don't see much harm in
leaving it in place for the moment.
Please let me know if you have any further information. Original comment by wmd...@gmail.com on 7 Jul 2010 at 11:28
Original issue reported on code.google.com by
benjamin...@gmail.comon 7 Jul 2010 at 7:54