On 0, Julien Danjou <a...@debian.org> wrote: > At 1207972098 time_t, Don Armstrong wrote: > > It would be nice if the awesome rc configuration file parser would > > throw warnings when problems in the configuration file are encountered > > instead of throwing out the entire configuration file and using only > > the defaults. > > > > The current status quo means that every upgrade which changes the > > configuration file parsing requires you to edit the configuration file > > to fix the first error, restart awesome, edit to fix the next, etc. It > > also means that any customization is lost until you fix your > > .awesomerc, which is anoying when you have rather different > > keybindings. > > What about awesome --check? >
This is (kind of) buggy or has weired behavior. $ awesome --check ✔ Configuration file syntax OK. $ vi .config/awesome/rc.lua (now, I introduce an abvious error in my rc.lua) $ awesome --check /home/dogguy/.config/awesome/rc.lua:62: '}' expected (to close '{' at line 53) near '[' ✔ Configuration file syntax OK. $ echo $? 0 Could be this fixed at least? - Do not show “✔ Configuration file syntax OK.” when it's not OK. - Do not exit with code 0 when it's not OK. Cheers, -- Mehdi Dogguy http://www.pps.jussieu.fr/~dogguy/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org