Hello, I'm up an running again, so thanks for the suggestion about the theme file. I had to express my feeling about the situation at the moment, so sorry if I insulted someone :).
Such breakages are to be expected if you're tracking git. You already > know that. Awesome is pretty much still work-in-progress, so such > changes may be even there when upgrading between same major number > versions. If there was a way for us to know a priori what's the best > design/implementation we would definitely had gone that way; if you do > happen to know some method, please share. > Well, I don't know. One thing I suggested back then was to split rc.lua into more files, like we have theme file. I'd be happy to have this with key bindings, so you could plug in your own key scheme without modyfying the rc.lua (expect for the key map file). Also what I don't like is to change the wibox layouts all the time. That would alse be nice to have this someplace else. But I know it's difficult to implement such things easily and make it work for most of the people... I can get away with this. You should check your xinitrc file and your console foo. Even if X gets > stuck like that, you can kill it by ctrl-alt-backspace, or you can > switch to a virtual console with ctrl-alt-Fn. If you had followed the > instructions on the wiki and docs, you should have the debugging output > somewhere handy. From there, you could fix your errors and restart or > reload awesome (pkill -HUP awesome). Note: because you didn't have a > graphical environment to play with this doesn't mean your computer is > locked up! > Ok, so once again, read this: > i updated my arch linux yesterday and when i rebooted (kernel update) and > run startx, awesome just crashed. so i thought - ok, it might be my old > awesome version from git, so i rebuilt latest git version of awesome. after > that, awesome starts up, but i get just a black screen with default x > cursor. i can't quit it, kill it, use ctrl-alt-backspace or even > ctrl-alt-del. i just have to use the power button. > Didn't I make myself clear? My system completly hung! Using awesome for some time, I already got used to the practice, that after update, awesome doesn't dig my rc.lua. It results usually in two things: 1. awesome doesn't start at all - didn't happen very often 2. awesome loads and stays in some intermediate state, just with background and no widgets, sometimes keys work (I could do Mod4-Ctrl-q), sometimes they don't In case 2, I know that I can use Alt-F1 to go back to the console, check the messages there, go to console 2, fix my rc.lua, pkill -HUP awesome, go back with Alt-F7 and see if it's fixed. Or I would while updating inside awesome go for nested Xephyr session and provide pass updated rc.lua to awesome there to test it. But what disappointed me was that it didn't happen this time!!! I say again, awesome just brought up BLACK SCREEN with X cursor without ANY POSSIBILITY I know of (no ctrl-alt-backspace, no alt-f1, no ctrl-alt-del) to bring it down and fix the config. awesome -k checks your config file for errors. According to the error > messages in your original email, the problem was in your theme file, not > your configuration file. Perhaps we should extend our testing chores to > that as well. > Yes, this has some bad untested code smell to me. It seems to me like when awesome parses the config files, it just stores the metadata, and builds the interface later from it. If you pass syntactically correct, but logically wrong data inside, it has no way of checking the mistake and nicely locks up. What I would expect is that it would crash, even with some unhandled exception, but not to lock up my system so bad. That's way too nasty. Sorry to hear that. awesome is an open source project so feel free to > correct whatever it is that you don't like and contribute your patches > back to this list. > I'd be happy to do that, but I lack the time to do so. It would require me to do some extensive resarch on lua's innards, how one does hook up his C program to lua machine, communicate method calls from C to lua and back and how does awesome use the X protocol and that funky X things around. I ended up when I encountered luaA* methods (enhanced lua standard functionality?). I was browsing the code when I was checking how I could extend the key binding concept to allow me to bind modifier key release sequences correctly (as you have in more complex WMs/DMs like M$ Windows :)). I'm not as skilled with linux programming pracitices as I would like to be, my bad :(. I browsed new lua.rc, I see the wibox/key stuff changed again. It changes every time I update. Will it ever stabilize... Regards, David On Wed, May 13, 2009 at 7:27 PM, Nikos Ntarmos <[email protected]> wrote: > On Wed, May 13, 2009 at 07:19:28PM +0200, dante4d wrote: > > well, ok, i tried to run awesome with default rc.lua. and it worked. > > so my conclusio here is: > > 1) as i already mentioned, the rc.lua changes that break my setup are > > horrible thing. the whole concept of this is a mess. ok, i do git > > version, but still... this is fucked up. BUT, > > Such breakages are to be expected if you're tracking git. You already > know that. Awesome is pretty much still work-in-progress, so such > changes may be even there when upgrading between same major number > versions. If there was a way for us to know a priori what's the best > design/implementation we would definitely had gone that way; if you do > happen to know some method, please share. > > > 2) having a bad config file causes awesome not to crash and say - ok, > > the config file is a mess, but lock up my system to the point that i > > can't do anything? that's even worse fuckup > > You should check your xinitrc file and your console foo. Even if X gets > stuck like that, you can kill it by ctrl-alt-backspace, or you can > switch to a virtual console with ctrl-alt-Fn. If you had followed the > instructions on the wiki and docs, you should have the debugging output > somewhere handy. From there, you could fix your errors and restart or > reload awesome (pkill -HUP awesome). Note: because you didn't have a > graphical environment to play with this doesn't mean your computer is > locked up! > > > 3) i tried to do awesome -k and it did say my config file is ok - so > > then, what's the point of that option if it doesn't help any? > > awesome -k checks your config file for errors. According to the error > messages in your original email, the problem was in your theme file, not > your configuration file. Perhaps we should extend our testing chores to > that as well. > > > guys, this is BAD. awesome let's me down once again... > > Sorry to hear that. awesome is an open source project so feel free to > correct whatever it is that you don't like and contribute your patches > back to this list. > > Cheers. > > \n\n >
