From b06b668dd6a020d19bcafca8e9dff8b2486019f8 Mon Sep 17 00:00:00 2001 From: "B. Watson" Date: Wed, 20 May 2020 03:03:46 -0400 Subject: nitpickery --- unsaver.html | 49 +++++++++++++++++++++++++++++-------------------- 1 file changed, 29 insertions(+), 20 deletions(-) (limited to 'unsaver.html') diff --git a/unsaver.html b/unsaver.html index 878eb10..17188e3 100644 --- a/unsaver.html +++ b/unsaver.html @@ -382,7 +382,7 @@ ul.auto-toc {

SYNOPSIS

-

unsaver [-i interval[s|ms]] [-m | -k keycode | -b button | -c command | -x ] [-j | -f] [-d] [joydev [joydev ...]]

+

unsaver [-i interval[s|ms]] [-m | -k keycode | -b button | -c command | -x ] [-j | -f] [-d] [joystick [joystick ...]]

DESCRIPTION

@@ -395,17 +395,22 @@ script your window manager or desktop environment uses. By default, it will exit when the X server does. There's no PID file: use "pkill unsaver" if you need to kill the daemon.

Every interval milliseconds (250, or whatever -i is set to), unsaver -checks to see if there's been any activity on any of the devices it's -monitoring. If so, it sends a fake mouse movement, keystroke, or mouse -button click, which the screen saver will see as activity.

-

Multiple joystick devices can be monitored. By default, unsaver -monitors up to 16 devices, named /dev/input/js0 through js15. -These devices don't have to actually exist: they can come and go -as joysticks are plugged in and unplugged. See JOYSTICK DEVICES -if the defaults don't work for you.

+checks to see if there's been any activity on any of the josticks, or +if a fullscreen window exists. If so, it deactivates the screensaver +by sending a keystroke, clicking a mouse button, moving the mouse, +or executing a command (see "Monitoring Options", below).

+

Multiple joystick devices can be monitored. By default, unsaver monitors +up to 16 joysticks. These devices don't have to actually exist: they +can come and go as joysticks are plugged in and unplugged. See JOYSTICK +DEVICES if the defaults don't work for you.

OPTIONS

+

With no options, the default interval is 250ms, the deactivation mode +is to send an otherwise-unused keycode, and both joystick and fullscreen +monitoring is enabled.

+

A space is required between an option and its argument, as shown +above. Use e.g. -i 300, not -i300.

General options

@@ -442,7 +447,7 @@ as milliseconds. Default: 250m.-f +joysticks are ignored with -f.
Only detect fullscreen windows; don't monitor joysticks. -j and -f are mutually exclusive. Note that -joydevs are ignored with -f.
@@ -483,8 +488,6 @@ option, to avoid excess process-spawning overhead. Same as -c "xscreensaver-command -deactivate" -i 1s. -

A space is required between an option and its argument, as shown -above. Use e.g. -i 300, not -i300.

@@ -511,6 +514,9 @@ a single monitor, and may not work properly in multi-head environments.

It's recommended to let unsaver find the joysticks itself. However, you can pass one or more joystick numbers if the default doesn't do the right thing for you. Remember that the first joystick is numbered 0, not 1.

+

One reason to manually set the joystick list might be that your 2nd +joystick is rarely used, and your cat likes to play with it. To monitor +only one device, you can say unsaver 0.

When you manually set the list of devices, unsaver will only detect hotplug events on the devices you gave it. If you plug in more joysticks, they won't be monitored.

@@ -525,10 +531,12 @@ the default names.

ENVIRONMENT

-
UNSAVER_JS_DIR Path to joystick device nodes. If your OS keeps them
-
somewhere besides "/dev/input", set this variable.
-
UNSAVER_JS_NODE Base name for joystick device nodes. "js" by default.
-
Don't set this to "event", unsaver doesn't speak the +
UNSAVER_JS_DIR
+
Path to joystick device nodes. If your OS keeps them +somewhere besides "/dev/input", set this variable.
+
UNSAVER_JS_NODE
+
Base name for joystick device nodes. "js" by default. +Don't set this to "event", unsaver doesn't speak the full Linux event protocol.
@@ -542,10 +550,10 @@ or else fork() failed. No daemon will be running in this case.

BUGS

-

There's no way to distinguish between an invalid device name and a -device name that doesn't happen to exist yet because its device hasn't +

There's no way to distinguish between an invalid device number and a +device number that doesn't happen to exist yet because its device hasn't been plugged in yet. Try to avoid typos, if you really have to use device -names (better to autodetect).

+numbers (it's better to autodetect).

Normally once daemonized, unsaver is very robust. However, if something does go wrong, there's no way to find out what. Probably there should be a log file, or use syslog (or is that overkill?).

@@ -577,7 +585,8 @@ to port the code.

SEE ALSO

-

jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2)

+

jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2), xscreensaver(1), +xautolock(1), xlock(1), xset(1)

-- cgit v1.2.3