summaryrefslogtreecommitdiff
path: root/COMPOSITOR
diff options
context:
space:
mode:
authorOlivier Fourdan <fourdan.olivier@wanadoo.fr>2005-01-18 18:33:00 +0000
committerOlivier Fourdan <fourdan.olivier@wanadoo.fr>2005-01-18 18:33:00 +0000
commit536e93de715b35e8f0dc18218769dd342ee0abec (patch)
treef0c4fe649c9cbb48142bfbbcc6d62828b775d4cb /COMPOSITOR
parentea8f99bce7c6c08bf08d6c71bc0586dab985a0d5 (diff)
downloadxfwm4-536e93de715b35e8f0dc18218769dd342ee0abec.tar.gz
Fix bug #611 (Documentation on command line option to enable/disable xfwm4 compositor)
(Old svn revision: 12296)
Diffstat (limited to 'COMPOSITOR')
-rw-r--r--COMPOSITOR4
1 files changed, 2 insertions, 2 deletions
diff --git a/COMPOSITOR b/COMPOSITOR
index 3da094b22..a3fa705c2 100644
--- a/COMPOSITOR
+++ b/COMPOSITOR
@@ -61,9 +61,9 @@ If you still think you have found a bug in xfwm4 compositing manager, here
are a few hints that could help categorizing the problem:
- Does it happen when xfwm4 compositor is disabled?
- ie, when running "xfwm4 --compositor=no"
+ ie, when running "xfwm4 --compositor=off"
- Does it happen with xcompmgr?
- ie, when running "xfwm4 --compositor=no; xcompmgr -c"
+ ie, when running "xfwm4 --compositor=off; xcompmgr -c"
- Does it show with the Xserver embedded compositor manager?
ie, when running "xfwm4 --compositor=auto"