On 19.05.2011 23:50, David J. Haines wrote:
I was wondering what the feasibility would be of having awesome.quit() close
all the clients before it exits. I ask because I know that some programs
need the window close signal (or its equivalent) to exit properly. Foremost
in my mind are VirtualBox machines, which don't take too kindly to a simple
SIGTERM or what-have-you, but which are all to happy to save state or send a
shutdown signal if you close them with, e.g. client.kill().
awesome doesn't do anything when it quits except, well, quitting. The problem is
most likely that your X server exits when the WM quits.
In the alternative, I'd be more than happy to just redefine awesome.quit(),
as I know Lua can do,[...]
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=738
(Looking at this again, instead of starting a timer it should just hook the
unmanage signal. Whatever....)
> [...] but putting in a redefinition in my rc.lua doesn't
> seem to have any effect.
The behavior for "awesome", "key", "button", "client", "timer" (and I bet I
forgot something else) are hardcoded in C. Those aren't lua tables which you can
modify. In fact, trying something like awesome.foo = bar should trigger the
debug::newindex::miss signals which announces that something fishy is going on.
Cheers,
Uli
--
- Buck, when, exactly, did you lose your mind?
- Three months ago. I woke up one morning married to a pineapple.
An ugly pineapple... But I loved her.
--
To unsubscribe, send mail to [email protected].
