Hi. On Thu 2009-01-22 15:03, Damien Leone <[email protected]> proclaimed: > On 22 Jan - 14:15, dante4d wrote: > > I wonder what you guys do when awesome changes it's rc.lua structure and > > your > > rc.lua stops working. I always have to hand check and rewrite my rc.lua, > > wasting about 30 minutes of time. Is that intended? > > If awesomerc.lua has changed a lot, I usually start by checking if my > rc.lua would still work by running awesome in a nested X server (such > as Xephyr), thus I won't crash my current session, then I would look > at the X errors log file (~/.xsession-errors, or Xephyr's output) > which will indicate me what lines of my config are not correct and > then compare it with the provided rc.lua.
I really like the idea of using Xephyr, but how do I control the awesome
within Xephyr - all my keybindings are caught by the "outer" awesome. Is
there some way of passing them through?
Btw I play around with the git version from time to time, or to check
for a (fixed) bug, but usually have a packaged version installed for
everyday use. When building the git version, everything installs into
some /usr/local directories as expected, with the exception of the
default rc.lua, which gets installed to /etc/xdg/awesome/. This
conflicts with the rc.lua that belongs to the package of my
distribution. Is this really necessary? Is there no local/ directory
where it could be put?
Greetings,
Frank
--
Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A
Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A
"Just because I don't care doesn't mean I don't understand."
(Homer Simpson)
signature.asc
Description: Digital signature
