Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Updated Bugs section in manpage.
|
|
fixes in there, please reapply.
Corrected manpage.
|
|
Documented SIGUSR2 for beryl-manager
beryl-xgl.1 now sources beryl.1, no need to maintain multiple files any more.
|
|
|
|
|
|
nuked anoying not found output of which. New startup scheme should be now complete. TODOnext: Don't detect via pidof, detect via X...
|
|
|
|
on a ClientMessage we have the popup (Maybe add additional checks if unwanted
popup apeear in the wild.). Multiple DISPLAY fixes.
It now, per default don't replaces a running Window Manager at start
(but you can use --force-window-manager).
--force-decorator effect stuff untested/disfunctional at the moment...
Some gdk_thread fixes, at least according to documentation.
At least lesser startup crashes in reloading WMs.
|
|
.beryl-manager.lock became .beryl-manager.DISPLAYNAME.pid, no flock() here, flock() doesn't work on NFS-mounted homedirs.
Function is_running() rewritten.
Don't create a Atom "WM_S0" anymore, if we don't get one,.
Minor code cleans, doc updated.
This is_running() stuff only work on the same machine, when having stuff running remote and parts from different machines, we are still in bigger trouble.
|
|
Trying to invoke multiple times will result in popping up the menu from already running instance.
|
|
|
|
should probably fix #434, prevents from respawning itself.
|
|
|
|
|