Emmanuel Lepage Vallee 1c177cabce awesomerc: Explicitly select a default screen ... A client is supposed to go to a screen when: * It has been started using `awful.spawn` with explicit instructions [1] * An `awful.rules` rule **or any of its callbacks** set the screen [2] * When something handle `request::screen` and/or `request::tag` in some custom ways. [3] * Some clients can request a screen and mean it (like MythTV/Kodi/XBMC and some multi-window DAW) [4] A client is supposed to go to the focused screen when none of the above are true [5]. Other constraints: * The screen need to be set only once, anything will will emit `property::screen` many time and cause side effects. * There has to be a single entry point to the algorithm, no multiple "manage" handler. * Awesome internals must use the `request::` signal API and not force their decision outside of request handlers. * Restarting Awesome must not change the client screen Commit 2178744 fix use case number [1] and [2]. It actually fix [4] too, but it is an accident and I am not sure we care about [4] anyway. Use case [1] and [2], however, are very important. Fix #1091		2016-09-21 22:15:09 +02:00
..
awful	awesomerc: Explicitly select a default screen	2016-09-21 22:15:09 +02:00
beautiful	Minor doc fixes	2016-03-06 14:46:13 +01:00
gears	wallpaper: Do not use the deprecated geometry access	2016-09-11 02:10:02 -04:00
menubar	menubar: Do not use the deprecated geometry access	2016-09-11 01:55:33 -04:00
naughty	wibox: Create a container module	2016-05-30 17:51:19 -04:00
wibox	drawable: Prevent collected drawables from being redrawn.	2016-09-07 00:41:10 -04:00