Allow 'background: unset'

When a user sets 'background: none' it really means "Do not let themes touch the
background I have already set with fbsetbg" -> It does still actually call
fbsetbeg to re-assert the proper background.

This new value 'unset' is for users who will use an alternate method to set
their background (root-tail, xscreensaver, or whatever).  It instructs fluxbox
to *never* run fbsetbg.

1 files changed, 5 insertions, 2 deletions

diff --git a/doc/asciidoc/fluxbox-style.txt b/doc/asciidoc/fluxbox-style.txt
index 02838fb..69a1d6d 100644
--- a/doc/asciidoc/fluxbox-style.txt
+++ b/doc/asciidoc/fluxbox-style.txt
@@ -361,9 +361,12 @@ resource to contain a valid file name. The `random' option requires
 `solid', and `mod' all require `background.color' to be set. `gradient' and
 `mod' both require `background.colorTo'. `mod' requires `background.modX' and
 `background.modY' to be set as well. These options will be passed to
-*fbsetroot(1)* to set the background.
+*fbsetroot(1)* to set the background. The special option `unset' is for use in
+user overlay files only. It specifies that fbsetbg should never be run (by
+default, even when `none' is set in the overlay, fluxbox will try to run
+``fbsetbg -z'' to restore the last wallpaper).
 
-   background: centered|aspect|tiled|fullscreen|random|solid|gradient <texture>|mod|none
+   background: centered|aspect|tiled|fullscreen|random|solid|gradient <texture>|mod|none|unset
    background.pixmap: <file or directory>
    background.color: <color>
    background.colorTo: <color>