Re: FVWM: Followup to the autofading for anyone interested...

From: Jim Knoble <jmknoble_at_intrex.net>
Date: Thu, 16 Apr 1998 15:12:14 -0400 (EDT)

>From the `xlock' manual page othat came with xlockmore-3.13:

       -/+enablesaver
            By default xlock will disable the normal X server's
            screen saver since it is in effect a replacement for
            it. Since it is possible to set delay parameters
            long enough to cause phosphor burn on some displays,
            this option will turn back on the default screen
            saver which is very careful to keep most of the
            screen black.

Note that `-enablesaver' enables the X screensaver, and `+enablesaver'
disables it. You can also set the corresponding resource in your
.Xdefaults file:

    XLock.enablesaver: off

--jim

%%%%%%%%%%%%%%% jim knoble %%%%%%%% jmknoble_at_pobox.com %%%%%%%%%%%%%%%%%

On Thu, 16 Apr 1998, Chris Jewell wrote:

: In order to get X11 to NOT fade to a blank screen when using xlockmore or
: any other xscreensaver you have to use the 'xset s off' command. Put this
: command in your .xintrc and it will trun off the auto fade screen saver
: for X11.
:
:
: -Chris Jewell
:
: --
: Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
: To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
: message to majordomo_at_hpc.uh.edu.
: To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
:
:
:

--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Apr 16 1998 - 13:17:04 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:01 BST