From 29f0434b2d5141db1d0b6b20be8967905fe85aa9 Mon Sep 17 00:00:00 2001
From: "B. Watson" <yalhcru@gmail.com>
Date: Tue, 19 May 2020 15:58:05 -0400
Subject: ...and lo, a Great Renaming came upon the land, the like of which
 shall not be seen again

---
 Makefile     |   6 +-
 jsmond.1     | 216 -----------------
 jsmond.c     | 754 -----------------------------------------------------------
 jsmond.html  | 559 --------------------------------------------
 jsmond.rst   | 195 ----------------
 unsaver.1    | 216 +++++++++++++++++
 unsaver.c    | 754 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 unsaver.html | 559 ++++++++++++++++++++++++++++++++++++++++++++
 unsaver.rst  | 195 ++++++++++++++++
 9 files changed, 1727 insertions(+), 1727 deletions(-)
 delete mode 100644 jsmond.1
 delete mode 100644 jsmond.c
 delete mode 100644 jsmond.html
 delete mode 100644 jsmond.rst
 create mode 100644 unsaver.1
 create mode 100644 unsaver.c
 create mode 100644 unsaver.html
 create mode 100644 unsaver.rst

diff --git a/Makefile b/Makefile
index 374ffbb..eb844f5 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,4 @@
-# GNU Makefile for jsmond
+# GNU Makefile for unsaver
 
 ####
 # Packagers: override these on the make command line as needed.
@@ -49,12 +49,12 @@ RST2HTML=rst2html4.py
 
 # Hopefully, no user-serviceable parts below this line.
 
-PROJ=jsmond
+PROJ=unsaver
 
 # the .rst is the authoritative source for the version number.
 VERSION=$(shell fgrep '.. |version| replace::' $(PROJ).rst | cut -d' ' -f4)
 
-DEFINES=-DVERSION=\"$(VERSION)\" -DMAX_STICKS=$(MAX_STICKS) -DJSNODE=\"$(JSNODE)\" -DEVENTDIR=\"$(EVENTDIR)\"
+DEFINES=-DVERSION=\"$(VERSION)\" -DMAX_STICKS=$(MAX_STICKS) -DJSNODE=\"$(JSNODE)\" -DEVENTDIR=\"$(EVENTDIR)\" -DPROJ=\"$(PROJ)\"
 
 CFLAGS+=$(shell pkg-config --cflags x11 xtst)
 LDFLAGS+=$(shell pkg-config --libs x11 xtst)
diff --git a/jsmond.1 b/jsmond.1
deleted file mode 100644
index 878839e..0000000
--- a/jsmond.1
+++ /dev/null
@@ -1,216 +0,0 @@
-.\" Man page generated from reStructuredText.
-.
-.TH JSMOND 1 "2020-05-19" "0.2.0" "Urchlay"
-.SH NAME
-jsmond \- deactivate screensaver on joystick activity
-.
-.nr rst2man-indent-level 0
-.
-.de1 rstReportMargin
-\\$1 \\n[an-margin]
-level \\n[rst2man-indent-level]
-level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
--
-\\n[rst2man-indent0]
-\\n[rst2man-indent1]
-\\n[rst2man-indent2]
-..
-.de1 INDENT
-.\" .rstReportMargin pre:
-. RS \\$1
-. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
-. nr rst2man-indent-level +1
-.\" .rstReportMargin post:
-..
-.de UNINDENT
-. RE
-.\" indent \\n[an-margin]
-.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
-.nr rst2man-indent-level -1
-.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
-.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
-..
-.\" RST source for jsmond(1) man page. Convert with:
-.
-.\" rst2man.py jsmond.rst > jsmond.1
-.
-.SH SYNOPSIS
-.sp
-jsmond [\fB\-i interval[s|ms]\fP] [\fB\-m\fP | \fB\-k keycode\fP | \fB\-b button\fP | \fB\-c command\fP | \fB\-x\fP ] [\fB\-d dir\fP] [\fB\-j name\fP] [\fB\-f\fP] [\fB\-F\fP] [\fB\-D\fP] [\fBjoydev [joydev ...]\fP]
-.SH DESCRIPTION
-.sp
-jsmond lets you play games with your joysticks/gamepads without the screen
-saver activating due to lack of keyboard/mouse input. It can also prevent
-the screensaver from activating when a fullscreen window is in use (e.g.
-while watching a movie).
-.sp
-Multiple joystick devices can be monitored. By default, jsmond
-monitors up to 16 devices, named /dev/input/js0 through js15.
-These devices don\(aqt have to actually exist: they can come and go
-as joysticks are plugged in and unplugged.
-.sp
-Every \fIinterval\fP milliseconds (250, or whatever \fB\-i\fP is set to), jsmond
-checks to see if there\(aqs been any activity on any of the devices it\(aqs
-monitoring. If so, it sends a fake mouse movement, keystroke, or mouse
-button click, which the screen saver will see as activity.
-.sp
-It\(aqs recommended to let jsmond find the joysticks itself. However,
-you can pass one or more device names (or just numbers) if the default
-doesn\(aqt do the right thing for you. In this case, only these devices
-will be monitored (no search is done).
-.sp
-jsmond should be started from your \fB\&.xinitrc\fP or whatever X startup
-script your window manager or desktop environment uses. By default, it
-will exit when the X server does. There\(aqs no PID file: use "pkill jsmond"
-if you need to kill the daemon.
-.SH OPTIONS
-.INDENT 0.0
-.TP
-.B \-\-help
-Print usage summary
-.TP
-.BI \-i \ <interval>
-Interval to check for activity. Can be given in seconds
-with \fIs\fP suffix (e.g. \fB1s\fP), or milliseconds with \fIm\fP
-(e.g. \fB200m\fP). If just a number is given, it\(aqs assumed
-to be in seconds if it\(aqs under 100, otherwise it\(aqs treated
-as milliseconds. Default: 250m.
-.TP
-.BI \-k \ <keycode>
-Send this keycode when activity is detected. Default
-is to search the keymap for an unused code. If you set this
-manually, it should be a keycode that \fIdoesn\(aqt\fP map to a keysym
-in your usual keymapping (use "xmodmap \-pk" to find one).
-.TP
-.BI \-b \ <button>
-Send a click of this button when activity is detected,
-rather than a keystroke. Should be a button that
-applications don\(aqt normally respond to (6 or higher),
-but in some environments, the window manager responds to
-all the \(aqextra\(aq buttons as though they were button 1.
-.TP
-.B \-m
-Send mouse movements rather than a keystroke. This will
-move the pointer 10 pixels to the right and down, then
-10 pixels to the left and up, then warp the pointer back
-to its starting point.
-.TP
-.BI \-c \ <command>
-Run a command when activity is detected, rather than
-sending a fake keystroke/click/motion. It\(aqs recommended
-to set \fIinterval\fP to at least 1 second when using this
-option, to avoid excess process\-spawning overhead.
-.TP
-.B \-x
-Same as \fB\-c "xscreensaver\-command \-deactivate" \-i 1s\fP\&.
-.TP
-.B \-f
-Deactivate screensaver if a fullscreen window is detected.
-This isn\(aqt likely to be 100% reliable yet.
-.TP
-.B \-F
-Same as \fB\-f\fP, but also disables joystick monitoring entirely.
-Note that \fB\-j\fP, \fB\-d\fP, and \fBjoydev\fP are ignored
-with this option.
-.UNINDENT
-.sp
-These options are intended for developers and  \fIreally\fP shouldn\(aqt be
-needed for normal use:
-.INDENT 0.0
-.TP
-.BI \-d \ <dir>
-Path to the directory containing joystick device nodes.
-Default is "/dev/input". This directory is monitored with
-inotify(7) so jsmond will be aware of hotplug events.
-.TP
-.BI \-j \ <name>
-Name of joystick device nodes, without any numeric
-suffix. Default is "js".
-.TP
-.B \-D
-Debug mode: run in foreground and print verbose messages.
-.UNINDENT
-.sp
-A space is required between an option and its argument, as shown
-above. Use e.g. \fB\-i 300\fP, not \fB\-i300\fP\&.
-.SH NOTES
-.sp
-jsmond was tested with xlock(1) and xscreensaver(1). All 3 modes
-(keycode, mouse click, and mouse motion) work with xscreensaver.
-xlock doesn\(aqt respond to mouse motion, so use the keycode or click
-modes with it.
-.sp
-jsmond can monitor up to MAX_STICKS joysticks. This is a compile time
-constant, normally set to 16. See the \fB\-\-help\fP output to find out
-the compiled\-in default.
-.sp
-\fBjoydev\fP arguments can be either a path to a device node (e.g.
-\fI/dev/input/js0\fP or similar), or a number, which will have the default
-device basename prepended to it. This is normally "/dev/input/js", but
-can be changed via the \fB\-d\fP and \fB\-j\fP options. Note that (currently)
-all the joystick devices have to be in the same directory for jsmond
-to detect hotplug events!
-.sp
-Note that it\(aqs \fInot\fP an error to give nonexistent joystick device names.
-jsmond will wait for devices to come into existence (e.g. as created
-by \fBudev\fP).
-.sp
-If the screensaver is configured to lock the screen, and it has already
-done so, pressing a joystick button/direction will just bring up the
-password dialog, same as pressing a key or mouse button would.
-.sp
-jsmond depends on the XTest extension being present in the X server. If
-you get a "X server doesn\(aqt support XTest extension" error, see your X
-server documentation to find out how to enable XTest.
-.sp
-The fullscreen window monitoring has only been tested on a system with
-a single monitor, and may not work properly in multi\-head environments.
-.SH EXIT STATUS
-.sp
-Without the \-D option, the exit status is 0 (success) if jsmond
-successfully forked into the background.
-.sp
-A non\-zero exit status means an error in the command line arguments,
-or else fork() failed. No daemon will be running in this case.
-.sp
-With the \-D option, jsmond never exits until it\(aqs killed.
-.SH BUGS
-.sp
-There\(aqs no way to distinguish between an invalid device name and a
-device name that doesn\(aqt happen to exist yet because its device hasn\(aqt
-been plugged in yet. Try to avoid typos, if you really have to use device
-names (better to autodetect).
-.sp
-Normally once daemonized, jsmond is very robust. However, if something
-does go wrong, there\(aqs no way to find out what. Probably there should
-be a log file, or use syslog (or is that overkill?).
-.sp
-It should be (but currently isn\(aqt) possible to at least work in
-mouse\-motion mode even without the XTest extension, via XWarpPointer().
-.sp
-jsmond isn\(aqt portable. It only works on Linux, at least for now, for
-three reasons:
-.INDENT 0.0
-.IP \(bu 2
-It uses the Linux joystick API.
-.IP \(bu 2
-It uses inotify(7) to detect joystick hotplug events.
-.IP \(bu 2
-I haven\(aqt even looked at other OSes to see if it would be possible
-to port the code.
-.UNINDENT
-.\" EXAMPLES
-.
-.\" ========
-.
-.SH LICENSE
-.sp
-jsmond is released under the WTFPL: Do WTF you want with this.
-.SH AUTHOR
-.sp
-jsmond was written by B. Watson <\fI\%yalhcru@gmail.com\fP>.
-.SH SEE ALSO
-.sp
-jstest(1), jscal(1), sdl\-jstest(1), sdl2\-jstest(2)
-.\" Generated by docutils manpage writer.
-.
diff --git a/jsmond.c b/jsmond.c
deleted file mode 100644
index a7b8d40..0000000
--- a/jsmond.c
+++ /dev/null
@@ -1,754 +0,0 @@
-/* need this, or else we don't get a prototype for strdup() from string.h */
-#define _XOPEN_SOURCE 500
-
-#include <string.h>
-#include <stdio.h>
-#include <unistd.h>
-#include <stdlib.h>
-#include <sys/types.h>
-#include <sys/stat.h>
-#include <fcntl.h>
-#include <limits.h>
-#include <errno.h>
-
-#include <X11/X.h>
-#include <X11/Xlib.h>
-#include <X11/extensions/XTest.h>
-
-#include <linux/joystick.h>
-#include <sys/inotify.h>
-
-/* microseconds to wait between sending a keypresss
-   or mouse click event and its release */
-#define EVENT_DELAY 100000
-
-/* if we can't find an unused keycode in the X keymap, use this one */
-#define FALLBACK_KEYCODE 255
-
-/* min/max allowed keycodes. really this should be queried from
-   the X server, but for Xorg this value is good enough for
-   argument checking. the max is 0xff as keycodes are 8 bit unsigned. */
-#define MIN_KEYCODE 8
-#define MAX_KEYCODE 255
-
-/* same as above, for mouse buttons. */
-#define MIN_BUTTON 1
-#define MAX_BUTTON 10
-
-/* command for -x */
-#define X_COMMAND "xscreensaver-command -deactivate"
-
-/* default "-i 250ms" */
-#define DEFAULT_INTERVAL 250
-
-typedef enum {
-	fm_auto_keycode, fm_keycode, fm_button, fm_motion, fm_cmd
-} fake_mode_t;
-
-/* user options */
-int interval = DEFAULT_INTERVAL; /* -i (always in millisec) */
-int debug = 0;                   /* -D */
-int keycode = -1;                /* -k */
-int button = -1;                 /* -b */
-char *event_dir = EVENTDIR;      /* -d */
-char *js_node_name = JSNODE;     /* -j */
-int autodiscover = 1; /* cleared if user supplies joydev args */
-fake_mode_t fake_mode = fm_auto_keycode;  /* -k, -b, -m */
-char *c_command = NULL;          /* -c, -x */
-int monitor_joysticks = 1;       /* -F */
-int monitor_fullscreen = 0;      /* -f, -F */
-
-/* joystick stuff */
-char *joynames[MAX_STICKS + 1];
-int last_joyname = 0;
-int joyfds[MAX_STICKS + 1];
-
-/* executable name, for warnings/errors */
-const char *self;
-
-/* X stuff */
-Display *xdisp;
-
-/* inotify stuff */
-int inotify_fd, watch_fd;
-char inotify_buf[sizeof(struct inotify_event) + NAME_MAX + 1];
-struct inotify_event *inotify_ev = (struct inotify_event *)inotify_buf;
-
-/* not going to include pages of usage info duplicating the man page */
-void usage(void) {
-	printf("jsmond v" VERSION " by B. Watson, WTFPL\n");
-	printf("Usage: %s [-i interval] [-b button | -k keycode] [-j name]\n", self);
-	printf("              [-d dir] [-D] [joystick [...]]\n");
-	printf("Built-in defaults: MAX_STICKS=%d, -d " EVENTDIR ", -j " JSNODE "\n", MAX_STICKS);
-	printf("See man page for details\n");
-	exit(0);
-}
-
-void die(const char *msg) {
-	fprintf(stderr, "%s: %s\n", self, msg);
-	exit(1);
-}
-
-/* make some trivial Xlib call that will result in Xlib killing
-   this process if it fails. XNoOp looks like it was meant for
-   exactly this, but it keeps returning 1 even if the X server is killed. */
-void ping_x_server(void) {
-	(void)XPending(xdisp);
-	if(debug) fprintf(stderr, "X server is still alive\n");
-}
-
-void send_fake_key(void) {
-	if(debug) fprintf(stderr, "sending keycode %d\n", keycode);
-
-	/* press... */
-	XTestFakeKeyEvent(xdisp, keycode, 1, 0L);
-	XSync(xdisp, 0);
-
-	/* ...wait 1/10 sec... */
-	usleep(EVENT_DELAY);
-
-	/* ...release */
-	XTestFakeKeyEvent(xdisp, keycode, 0, 0L);
-	XSync(xdisp, 0);
-}
-
-void send_fake_click(void) {
-	if(debug) fprintf(stderr, "sending button %d click\n", button);
-
-	/* press... */
-	XTestFakeButtonEvent(xdisp, button, 1, 0L);
-	XSync(xdisp, 0);
-
-	/* ...wait 1/10 sec... */
-	usleep(EVENT_DELAY);
-
-	/* ...release */
-	XTestFakeButtonEvent(xdisp, button, 0, 0L);
-	XSync(xdisp, 0);
-}
-
-/* XXX: the man page documents XTestFakeRelativeMotionEvent()
-   as taking 5 arguments (2nd one is screen_number), but Xtst.h
-	only has 4 (with no screen_number arg). */
-void send_fake_motion(void) {
-	int oldx, oldy, ignoreme;
-	Window win_ignoreme;
-
-	if(debug) fprintf(stderr, "sending mouse motion\n");
-
-	XQueryPointer(
-			xdisp,
-			DefaultRootWindow(xdisp),
-			&win_ignoreme,
-			&win_ignoreme,
-			&oldx,
-			&oldy,
-			&ignoreme,
-			&ignoreme,
-			(unsigned int *)&ignoreme);
-
-	if(debug) fprintf(stderr, "oldx %d, oldy %d\n", oldx, oldy);
-
-	/* move... */
-	XTestFakeRelativeMotionEvent(xdisp, 10, 10, 0L);
-	XSync(xdisp, 0);
-
-	/* ...wait 1/10 sec... */
-	usleep(EVENT_DELAY);
-
-	/* ...move back */
-	XTestFakeRelativeMotionEvent(xdisp, -10, -10, 0L);
-	XSync(xdisp, 0);
-
-	/* we've moved all 4 directions now. but if were were too close
-	   to an edge of the screen, the mouse pointer isn't where it
-	   started. so: */
-	XWarpPointer(
-			xdisp,
-			None,
-			DefaultRootWindow(xdisp),
-			0,
-			0,
-			0,
-			0,
-			oldx,
-			oldy);
-	XSync(xdisp, 0);
-}
-
-void exec_command(void) {
-	if(!c_command)
-		die("BUG: c_command is NULL\n");
-
-	if(debug) fprintf(stderr, "executing \"%s\"\n", c_command);
-	system(c_command);
-}
-
-void send_fake_x_event(void) {
-	switch(fake_mode) {
-		case fm_keycode:
-			send_fake_key();
-			break;
-		case fm_button:
-			send_fake_click();
-			break;
-		case fm_motion:
-			send_fake_motion();
-			break;
-		case fm_cmd:
-			exec_command();
-			break;
-		default: /* This Never Happens(tm) */
-			fprintf(stderr, "%s: BUG: fake_mode %d isn't a valid fake_mode_t!\n",
-					self, fake_mode);
-			exit(1);
-			break;
-	}
-}
-
-void open_joysticks(void) {
-	int fdcount, i;
-	struct js_event e;
-
-	fdcount = 0;
-	for(i = 0; i < last_joyname; i++) {
-		int synthev = 0;
-		if(joyfds[i] > -1) close(joyfds[i]);
-		joyfds[i] = open(joynames[i], O_RDONLY | O_NONBLOCK);
-		if(joyfds[i] > -1) {
-			fdcount++;
-			while( (read(joyfds[i], &e, sizeof(e)) > 0) && (e.type & JS_EVENT_INIT) )
-				synthev++;
-			if(debug)
-				fprintf(stderr, "opened %s, fd %d, skipped %d synthetic events\n",
-						joynames[i], joyfds[i], synthev);
-		}
-	}
-	if(debug) fprintf(stderr, "opened %d devices\n", fdcount);
-}
-
-void check_inotify() {
-	int res;
-
-	res = read(inotify_fd, inotify_buf, sizeof(inotify_buf) + NAME_MAX + 1);
-
-	if(res > 0) {
-		if(debug) {
-			fprintf(stderr, "read %d bytes from inotify_fd\n", res);
-			if(!inotify_ev->len) {
-				fprintf(stderr, "got event with no name: 0x%x\n", inotify_ev->mask);
-			} else {
-				fprintf(stderr, "got event with name %s: 0x%x\n", inotify_ev->name, inotify_ev->mask);
-			}
-		}
-
-		/* not much we can do to recover from this: */
-		if(inotify_ev->mask & IN_DELETE_SELF) {
-			die("someone deleted our device directory!");
-		}
-
-		/* ...or this: */
-		if(inotify_ev->mask & IN_UNMOUNT) {
-			die("someone unmounted our device directory!");
-		}
-
-		usleep(EVENT_DELAY); /* might not need, be paranoid */
-		open_joysticks();
-	} else {
-		if(errno != EAGAIN) {
-			/* not sure what could cause this, so no idea how/if we
-			   recover from it */
-			fprintf(stderr, "%s: failed to read from inotify_fd: %s\n",
-					self, strerror(errno));
-			exit(1);
-		}
-	}
-}
-
-int get_joystick_activity(void) {
-	struct js_event e;
-	int i, active = 0;
-
-	for(i = 0; i < last_joyname; i++) {
-		if(joyfds[i] < 0) continue;
-
-		if(debug) fprintf(stderr, "reading device %d, fd %d\n", i, joyfds[i]);
-
-		/* count events. any we get here *should* be real, but it doesn't
-			hurt to mask out synthetic ones again */
-		while(read(joyfds[i], &e, sizeof(e)) > 0) {
-			if(!(e.type & JS_EVENT_INIT)) active++;
-		}
-
-		/* EAGAIN just means there are no more events to read.
-			anything else is a problem, though not fatal */
-		if(errno != EAGAIN) {
-			if(debug) fprintf(stderr, "got error on device %d: %s\n", i, strerror(errno));
-		}
-	}
-
-	return active;
-}
-
-/* supposedly we could use the X window property _NET_WINDOW_FULLSCREEN
-   to detect a fullscreen window, but not everything actually sets that.
-   so a fullscreen window is defined here as:
-   - visible
-   - is the size of the root window
-   - and has input focus.
-*/
-int have_fullscreen_window(void) {
-	Window w;
-	XWindowAttributes w_attrs, root_attrs;
-	int revert_to;
-
-	/* man page doesn't document the actual
-	   return value, it says "int", is it really a Status? */
-	if(!XGetInputFocus(xdisp, &w, &revert_to)) {
-		if(debug) fprintf(stderr, "XGetInputFocus() failed\n");
-		return 0;
-	}
-
-	/* no window has focus (not an error) */
-	if(w == None)
-		return 0;
-
-	/* TODO: under what conditions does this fail? if it does fail once,
-		will it ever succeed again?
-
-		Hopefully, using w_attrs.root will do the right thing in multi-screen
-		environments. I can't easily test it though. */
-	if( XGetWindowAttributes(xdisp, w, &w_attrs) &&
-	    XGetWindowAttributes(xdisp, w_attrs.root, &root_attrs) )
-	{
-
-		if(debug)
-			fprintf(stderr,
-					"window id 0x%x (root 0x%x) has focus, map_state %d, geometry %dx%d\n",
-					(int)w, (int)w_attrs.root, w_attrs.map_state, w_attrs.width, w_attrs.height);
-
-		if( (w_attrs.map_state == IsViewable) &&
-				(root_attrs.width == w_attrs.width) &&
-				(root_attrs.height == w_attrs.height) )
-		{
-			if(debug) fprintf(stderr,
-					"window id 0x%x has input focus and looks fullscreen (%dx%d)\n",
-					(int)w, w_attrs.width, w_attrs.height);
-			return 1;
-		}
-	} else if(debug) {
-		if(debug) fprintf(stderr, "XGetWindowAttributes() failed\n");
-		return 0;
-	}
-
-	return 0;
-}
-
-/* this is the point of no return. the only way out of main_loop()
-   is process death. */
-void main_loop(void) {
-	int sleep_us;
-
-	sleep_us = interval * 1000;
-	fprintf(stderr, "entering main_loop(), sleep_us %d\n", sleep_us);
-
-	while(1) {
-		int active = 0;
-
-		/* Xlib will obligingly kill us, if X goes away */
-		ping_x_server();
-
-		/* check_inotify() will close & reopen the joystick fds as needed */
-		if(monitor_joysticks)
-			check_inotify();
-
-		/* let the fds gather events as we slumber */
-		if(debug) fprintf(stderr, "sleeping %dms...\n", interval);
-		usleep(sleep_us);
-
-		/* now see if any of them got any events while we took a nap */
-		if(monitor_joysticks)
-			active += get_joystick_activity();
-
-		if(monitor_fullscreen)
-			active += have_fullscreen_window();
-
-		/* if we got any activity on any of the fds, do our thing */
-		if(active) {
-			if(debug) fprintf(stderr, "*** got activity!\n");
-			send_fake_x_event();
-		} else if(debug) fprintf(stderr, "no activity\n");
-	}
-}
-
-/* make self point to our executable name without any directory */
-void set_exe_name(const char *argv0) {
-	const char *p;
-	self = argv0;
-	for(p = self; *p; p++)
-		if(p[0] == '/' && p[1]) self = p + 1;
-}
-
-char *make_joystick_name(int js) {
-	static char buf[PATH_MAX + 1];
-	sprintf(buf, "%s/%s%d", event_dir, js_node_name, js);
-	return buf;
-}
-
-/* add a joystick by pathname or number. note this only gets
-   called once, at startup: the list never gets modified after that. */
-void add_joystick_name(const char *name) {
-	if(last_joyname >= MAX_STICKS) {
-		fprintf(stderr,
-				"%s: too many device names, monitoring only the first %d\n",
-				self,
-				last_joyname);
-		return;
-	}
-
-	if(*name >= '0' && *name <= '9') {
-		add_joystick_name(make_joystick_name(atoi(name)));
-		return;
-	}
-
-	if( !(joynames[last_joyname] = strdup(name)) )
-		die(strerror(errno));
-
-	if(debug)
-		fprintf(stderr, "added device name %d: %s\n", last_joyname, name);
-
-	last_joyname++;
-}
-
-void populate_joynames(void) {
-	int i;
-
-	for(i = 0; i < MAX_STICKS; i++) {
-		add_joystick_name(make_joystick_name(i));
-	}
-}
-
-void set_fake_mode(fake_mode_t newmode) {
-	if(fake_mode != fm_auto_keycode)
-		die("use only one of the -k -b -m options");
-	else
-		fake_mode = newmode;
-}
-
-int set_interval(const char *arg) {
-	char *end;
-
-	interval = strtol(arg, &end, 0);
-
-	/* no digits at all */
-	if(end == arg) return 0;
-
-	/* no 0 or negative */
-	if(interval < 1) return 0;
-
-	/* digits only */
-	switch(*end) {
-		case '\0':
-			/* digits only, try to guess */
-			if(interval < 100) {
-				fprintf(stderr,
-						"%s: treating -i %d as %d seconds (use -i %dms if you meant %dms)\n",
-						self, interval, interval, interval, interval);
-				/* fall through */
-			} else {
-				break;
-			}
-		case 's':  interval *= 1000; break; /* sec */
-		case 'm':  break; /* ms, use as-is */
-	}
-
-	if(debug) fprintf(stderr, "interval set to %dms\n", interval);
-	return 1;
-}
-
-void parse_args(int argc, char **argv) {
-	char *nextarg;
-
-	if(argc > 1 && strcmp(argv[1], "--help") == 0) usage();
-
-	while(++argv, --argc) {
-		if(argv[0][0] != '-') {
-			/* no dash, treat as a joystick device */
-			add_joystick_name(*argv);
-			autodiscover = 0;
-		} else {
-			if(argv[0][1] && argv[0][2])
-				die("spaces required between options and arguments, please");
-			nextarg = argv[1];
-			switch(argv[0][1]) {
-				case 'm':
-					set_fake_mode(fm_motion);
-					break;
-				case 'k':
-					if(nextarg &&
-							(keycode = atoi(nextarg)) &&
-							(keycode >= MIN_KEYCODE) &&
-							(keycode <= MAX_KEYCODE) )
-					{
-						set_fake_mode(fm_keycode);
-						argv++, argc--;
-					} else {
-						fprintf(stderr, "%s: -k requires a keycode argument, %d-%d\n",
-								self, MIN_KEYCODE, MAX_KEYCODE);
-						exit(1);
-					}
-					break;
-				case 'b':
-					if(nextarg) button = atoi(nextarg);
-					if ( (button >= MIN_BUTTON) && (button <= MAX_BUTTON) ) {
-						set_fake_mode(fm_button);
-						argv++, argc--;
-					} else {
-						fprintf(stderr, "%s: -b requires a mouse button argument, %d-%d\n",
-								self, MIN_BUTTON, MAX_BUTTON);
-						exit(1);
-					}
-					break;
-				case 'i':
-					if(nextarg && set_interval(nextarg))
-						argv++, argc--;
-					else
-						die("-i requires a positive integer argument in milliseconds");
-					break;
-				case 'd':
-					if(nextarg) {
-						event_dir = nextarg;
-						argv++, argc--;
-					} else {
-						die("-d requires a directory argument");
-					}
-					break;
-				case 'j':
-					if(nextarg) {
-						js_node_name = nextarg;
-						argv++, argc--;
-					} else {
-						die("-j requires a string argument");
-					}
-					break;
-				case 'D':
-					debug = 1;
-					break;
-				case 'c':
-					if(nextarg) {
-						set_fake_mode(fm_cmd);
-						c_command = nextarg;
-						argv++, argc--;
-					} else {
-						die("-c requires a command argument");
-					}
-					break;
-				case 'x':
-					set_fake_mode(fm_cmd);
-					c_command = X_COMMAND;
-					break;
-				case 'F':
-					monitor_joysticks = 0; /* and fall thru */
-				case 'f':
-					monitor_fullscreen = 1;
-					break;
-				default:
-					die("unrecognized argument, try --help");
-					break;
-			}
-		}
-	}
-}
-
-/* make ourselves a daemon, double-fork technique.
-   verbose comments are not here because I think you need them, they're
-   here for me so I don't forget what this gibberish is for... */
-void daemonize(void) {
-	pid_t pid;
-
-	if((pid = fork()) < 0) {
-		/* in parent, fork failed */
-		fprintf(stderr, "%s: %s\n", self, strerror(errno));
-		die("failed to daemonize");
-	} else if(pid) {
-		/* in parent, fork succeeded */
-		exit(0);
-	}
-
-	/* now we're in the child, aka the 2nd generation parent.
-      the only reason for the first fork() was because setsid() can't
-	   be run in the parent process */
-	if( (setsid() < 0) ) {
-		fprintf(stderr, "%s: %s\n", self, strerror(errno));
-		die("failed to daemonize");
-	}
-
-	/* go on, do it again */
-	if((pid = fork()) < 0) {
-		/* in 2nd gen parent, fork failed */
-		fprintf(stderr, "%s: %s\n", self, strerror(errno));
-		die("failed to daemonize");
-	} else if(pid) {
-		/* in 2nd gen parent, fork succeeded */
-		fprintf(stderr, "%s: daemonized, PID %u\n", self, pid);
-		exit(0);
-	}
-
-	/* now we're in the grandchild, and we no longer need stdin/out/err */
-	close(0);
-	close(1);
-	close(2);
-
-	/* do this so we don't keep a filesystem from being umounted because
-		it's still busy (as our cwd) */
-	chdir("/");
-}
-
-/* helpers for init_* functions */
-void connect_to_x(void) {
-	int ignoreme;
-
-	if(debug) fprintf(stderr, "connecting to X server...\n");
-
-	xdisp = XOpenDisplay(getenv("DISPLAY"));
-
-	if(!xdisp) die("can't connect to X server");
-	if(debug) fprintf(stderr, "connected to X server\n");
-
-	if(XTestQueryExtension(xdisp, &ignoreme, &ignoreme, &ignoreme, &ignoreme)) {
-		if(debug) fprintf(stderr, "X server supports XTest extension, good\n");
-	} else {
-		die("X server doesn't support XTest extension\n");
-	}
-}
-
-/* XXX: XKeycodeToKeysym() is deprecated. I must learn XKB. */
-#pragma GCC diagnostic push
-#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
-KeySym get_keysym(int i) {
-	return XKeycodeToKeysym(xdisp, i, 0);
-}
-#pragma GCC diagnostic pop
-
-/* the goggles, they do nothing! */
-void find_keycode() {
-	int i, min_code = 0, max_code = 0;
-	
-	/* man page doesn't document the return value */
-	(void)XDisplayKeycodes(xdisp, &min_code, &max_code);
-
-	if(debug) fprintf(stderr, "XDisplayKeycodes min %d, max %d\n", min_code, max_code);
-
-	for(i = min_code; i <= max_code; i++) {
-		if(get_keysym(i) == NoSymbol) {
-			keycode = i;
-			if(debug) fprintf(stderr, "using keycode %d\n", keycode);
-			break;
-		}
-	}
-
-	if(keycode < 0) {
-		fprintf(stderr,
-				"%s: can't find a free keycode in the keymap, using %d\n",
-				self, FALLBACK_KEYCODE);
-		keycode = FALLBACK_KEYCODE;
-	}
-}
-
-/* the device name check is mostly to guard against typos */
-void check_joyname(int i) {
-	if(joynames[i] && (strncmp(event_dir, joynames[i], strlen(event_dir)) != 0)) {
-		fprintf(stderr, "%s: device %s is not in event dir %s\n",
-				self, joynames[i], event_dir);
-		exit(1);
-	}
-}
-
-/* init_* functions. these are only called once each, from main() */
-void init_joysticks(void) {
-	int i;
-
-	for(i = 0; i < MAX_STICKS; i++) {
-		joyfds[i] = -1;
-		check_joyname(i);
-	}
-
-	open_joysticks();
-}
-
-void init_inotify(void) {
-	inotify_fd = inotify_init1(IN_NONBLOCK);
-	if(inotify_fd < 0) {
-		fprintf(stderr, "%s: inotify_init1() failed: %s",
-				self, strerror(errno));
-		exit(1);
-	}
-
-	if(debug) fprintf(stderr, "inotify_init1() returned %d\n", inotify_fd);
-
-	watch_fd = inotify_add_watch(
-			inotify_fd,
-			event_dir,
-			IN_CREATE | IN_DELETE | IN_DELETE_SELF);
-
-	if(watch_fd < 0) {
-		fprintf(stderr, "%s: inotify_add_watch(\"%s\") failed: %s\n",
-				self, event_dir, strerror(errno));
-		exit(1);
-	}
-
-	if(debug) fprintf(stderr, "inotify_add_watch() on %s returned %d\n", event_dir, inotify_fd);
-}
-
-void init_x(void) {
-	connect_to_x();
-
-	if(fake_mode == fm_auto_keycode) {
-		find_keycode();
-		fake_mode = fm_keycode;
-	}
-
-	/* do this now, before daemonizing. if something's wrong, Xlib
-	   will kill us. we'd better let that happen while we still have a
-	   stderr, so the user can see what happened. */
-	send_fake_x_event();
-}
-
-void print_banner() {
-	const char *m;
-
-	if(monitor_joysticks && monitor_fullscreen) {
-		m = "joysticks and fullscreen";
-	} else if(monitor_joysticks) {
-		m = "joysticks only";
-	} else if(monitor_fullscreen) {
-		m = "fullscreen only";
-	} else {
-		die("nothing to monitor!");
-	}
-
-	fprintf(stderr, "%s: v%s monitoring %s, interval %dms\n",
-			self, VERSION, m, interval);
-}
-
-int main(int argc, char **argv) {
-	set_exe_name(argv[0]);
-
-	parse_args(argc, argv);
-
-	print_banner();
-
-	if(monitor_joysticks) {
-		if(autodiscover) populate_joynames();
-		init_joysticks();
-		init_inotify();
-	}
-
-	init_x();
-
-	if(!debug) daemonize();
-
-	main_loop();
-
-	return 0;
-}
diff --git a/jsmond.html b/jsmond.html
deleted file mode 100644
index 370edac..0000000
--- a/jsmond.html
+++ /dev/null
@@ -1,559 +0,0 @@
-<?xml version="1.0" encoding="utf-8" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.14: http://docutils.sourceforge.net/" />
-<title>jsmond</title>
-<meta name="date" content="2020-05-19" />
-<style type="text/css">
-
-/*
-:Author: David Goodger (goodger@python.org)
-:Id: $Id: html4css1.css 7952 2016-07-26 18:15:59Z milde $
-:Copyright: This stylesheet has been placed in the public domain.
-
-Default cascading style sheet for the HTML output of Docutils.
-
-See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
-customize this style sheet.
-*/
-
-/* used to remove borders from tables and images */
-.borderless, table.borderless td, table.borderless th {
-  border: 0 }
-
-table.borderless td, table.borderless th {
-  /* Override padding for "table.docutils td" with "! important".
-     The right padding separates the table cells. */
-  padding: 0 0.5em 0 0 ! important }
-
-.first {
-  /* Override more specific margin styles with "! important". */
-  margin-top: 0 ! important }
-
-.last, .with-subtitle {
-  margin-bottom: 0 ! important }
-
-.hidden {
-  display: none }
-
-.subscript {
-  vertical-align: sub;
-  font-size: smaller }
-
-.superscript {
-  vertical-align: super;
-  font-size: smaller }
-
-a.toc-backref {
-  text-decoration: none ;
-  color: black }
-
-blockquote.epigraph {
-  margin: 2em 5em ; }
-
-dl.docutils dd {
-  margin-bottom: 0.5em }
-
-object[type="image/svg+xml"], object[type="application/x-shockwave-flash"] {
-  overflow: hidden;
-}
-
-/* Uncomment (and remove this text!) to get bold-faced definition list terms
-dl.docutils dt {
-  font-weight: bold }
-*/
-
-div.abstract {
-  margin: 2em 5em }
-
-div.abstract p.topic-title {
-  font-weight: bold ;
-  text-align: center }
-
-div.admonition, div.attention, div.caution, div.danger, div.error,
-div.hint, div.important, div.note, div.tip, div.warning {
-  margin: 2em ;
-  border: medium outset ;
-  padding: 1em }
-
-div.admonition p.admonition-title, div.hint p.admonition-title,
-div.important p.admonition-title, div.note p.admonition-title,
-div.tip p.admonition-title {
-  font-weight: bold ;
-  font-family: sans-serif }
-
-div.attention p.admonition-title, div.caution p.admonition-title,
-div.danger p.admonition-title, div.error p.admonition-title,
-div.warning p.admonition-title, .code .error {
-  color: red ;
-  font-weight: bold ;
-  font-family: sans-serif }
-
-/* Uncomment (and remove this text!) to get reduced vertical space in
-   compound paragraphs.
-div.compound .compound-first, div.compound .compound-middle {
-  margin-bottom: 0.5em }
-
-div.compound .compound-last, div.compound .compound-middle {
-  margin-top: 0.5em }
-*/
-
-div.dedication {
-  margin: 2em 5em ;
-  text-align: center ;
-  font-style: italic }
-
-div.dedication p.topic-title {
-  font-weight: bold ;
-  font-style: normal }
-
-div.figure {
-  margin-left: 2em ;
-  margin-right: 2em }
-
-div.footer, div.header {
-  clear: both;
-  font-size: smaller }
-
-div.line-block {
-  display: block ;
-  margin-top: 1em ;
-  margin-bottom: 1em }
-
-div.line-block div.line-block {
-  margin-top: 0 ;
-  margin-bottom: 0 ;
-  margin-left: 1.5em }
-
-div.sidebar {
-  margin: 0 0 0.5em 1em ;
-  border: medium outset ;
-  padding: 1em ;
-  background-color: #ffffee ;
-  width: 40% ;
-  float: right ;
-  clear: right }
-
-div.sidebar p.rubric {
-  font-family: sans-serif ;
-  font-size: medium }
-
-div.system-messages {
-  margin: 5em }
-
-div.system-messages h1 {
-  color: red }
-
-div.system-message {
-  border: medium outset ;
-  padding: 1em }
-
-div.system-message p.system-message-title {
-  color: red ;
-  font-weight: bold }
-
-div.topic {
-  margin: 2em }
-
-h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
-h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
-  margin-top: 0.4em }
-
-h1.title {
-  text-align: center }
-
-h2.subtitle {
-  text-align: center }
-
-hr.docutils {
-  width: 75% }
-
-img.align-left, .figure.align-left, object.align-left, table.align-left {
-  clear: left ;
-  float: left ;
-  margin-right: 1em }
-
-img.align-right, .figure.align-right, object.align-right, table.align-right {
-  clear: right ;
-  float: right ;
-  margin-left: 1em }
-
-img.align-center, .figure.align-center, object.align-center {
-  display: block;
-  margin-left: auto;
-  margin-right: auto;
-}
-
-table.align-center {
-  margin-left: auto;
-  margin-right: auto;
-}
-
-.align-left {
-  text-align: left }
-
-.align-center {
-  clear: both ;
-  text-align: center }
-
-.align-right {
-  text-align: right }
-
-/* reset inner alignment in figures */
-div.align-right {
-  text-align: inherit }
-
-/* div.align-center * { */
-/*   text-align: left } */
-
-.align-top    {
-  vertical-align: top }
-
-.align-middle {
-  vertical-align: middle }
-
-.align-bottom {
-  vertical-align: bottom }
-
-ol.simple, ul.simple {
-  margin-bottom: 1em }
-
-ol.arabic {
-  list-style: decimal }
-
-ol.loweralpha {
-  list-style: lower-alpha }
-
-ol.upperalpha {
-  list-style: upper-alpha }
-
-ol.lowerroman {
-  list-style: lower-roman }
-
-ol.upperroman {
-  list-style: upper-roman }
-
-p.attribution {
-  text-align: right ;
-  margin-left: 50% }
-
-p.caption {
-  font-style: italic }
-
-p.credits {
-  font-style: italic ;
-  font-size: smaller }
-
-p.label {
-  white-space: nowrap }
-
-p.rubric {
-  font-weight: bold ;
-  font-size: larger ;
-  color: maroon ;
-  text-align: center }
-
-p.sidebar-title {
-  font-family: sans-serif ;
-  font-weight: bold ;
-  font-size: larger }
-
-p.sidebar-subtitle {
-  font-family: sans-serif ;
-  font-weight: bold }
-
-p.topic-title {
-  font-weight: bold }
-
-pre.address {
-  margin-bottom: 0 ;
-  margin-top: 0 ;
-  font: inherit }
-
-pre.literal-block, pre.doctest-block, pre.math, pre.code {
-  margin-left: 2em ;
-  margin-right: 2em }
-
-pre.code .ln { color: grey; } /* line numbers */
-pre.code, code { background-color: #eeeeee }
-pre.code .comment, code .comment { color: #5C6576 }
-pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
-pre.code .literal.string, code .literal.string { color: #0C5404 }
-pre.code .name.builtin, code .name.builtin { color: #352B84 }
-pre.code .deleted, code .deleted { background-color: #DEB0A1}
-pre.code .inserted, code .inserted { background-color: #A3D289}
-
-span.classifier {
-  font-family: sans-serif ;
-  font-style: oblique }
-
-span.classifier-delimiter {
-  font-family: sans-serif ;
-  font-weight: bold }
-
-span.interpreted {
-  font-family: sans-serif }
-
-span.option {
-  white-space: nowrap }
-
-span.pre {
-  white-space: pre }
-
-span.problematic {
-  color: red }
-
-span.section-subtitle {
-  /* font-size relative to parent (h1..h6 element) */
-  font-size: 80% }
-
-table.citation {
-  border-left: solid 1px gray;
-  margin-left: 1px }
-
-table.docinfo {
-  margin: 2em 4em }
-
-table.docutils {
-  margin-top: 0.5em ;
-  margin-bottom: 0.5em }
-
-table.footnote {
-  border-left: solid 1px black;
-  margin-left: 1px }
-
-table.docutils td, table.docutils th,
-table.docinfo td, table.docinfo th {
-  padding-left: 0.5em ;
-  padding-right: 0.5em ;
-  vertical-align: top }
-
-table.docutils th.field-name, table.docinfo th.docinfo-name {
-  font-weight: bold ;
-  text-align: left ;
-  white-space: nowrap ;
-  padding-left: 0 }
-
-/* "booktabs" style (no vertical lines) */
-table.docutils.booktabs {
-  border: 0px;
-  border-top: 2px solid;
-  border-bottom: 2px solid;
-  border-collapse: collapse;
-}
-table.docutils.booktabs * {
-  border: 0px;
-}
-table.docutils.booktabs th {
-  border-bottom: thin solid;
-  text-align: left;
-}
-
-h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
-h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
-  font-size: 100% }
-
-ul.auto-toc {
-  list-style-type: none }
-
-</style>
-</head>
-<body>
-<div class="document" id="jsmond">
-<h1 class="title">jsmond</h1>
-<h2 class="subtitle" id="deactivate-screensaver-on-joystick-activity">deactivate screensaver on joystick activity</h2>
-<table class="docinfo" frame="void" rules="none">
-<col class="docinfo-name" />
-<col class="docinfo-content" />
-<tbody valign="top">
-<tr class="manual-section field"><th class="docinfo-name">Manual section:</th><td class="field-body">1</td>
-</tr>
-<tr class="manual-group field"><th class="docinfo-name">Manual group:</th><td class="field-body">Urchlay</td>
-</tr>
-<tr><th class="docinfo-name">Date:</th>
-<td>2020-05-19</td></tr>
-<tr><th class="docinfo-name">Version:</th>
-<td>0.2.0</td></tr>
-</tbody>
-</table>
-<!-- RST source for jsmond(1) man page. Convert with: -->
-<!-- rst2man.py jsmond.rst > jsmond.1 -->
-<div class="section" id="synopsis">
-<h1>SYNOPSIS</h1>
-<p>jsmond [<strong>-i interval[s|ms]</strong>] [<strong>-m</strong> | <strong>-k keycode</strong> | <strong>-b button</strong> | <strong>-c command</strong> | <strong>-x</strong> ] [<strong>-d dir</strong>] [<strong>-j name</strong>] [<strong>-f</strong>] [<strong>-F</strong>] [<strong>-D</strong>] [<strong>joydev [joydev ...]</strong>]</p>
-</div>
-<div class="section" id="description">
-<h1>DESCRIPTION</h1>
-<p>jsmond lets you play games with your joysticks/gamepads without the screen
-saver activating due to lack of keyboard/mouse input. It can also prevent
-the screensaver from activating when a fullscreen window is in use (e.g.
-while watching a movie).</p>
-<p>Multiple joystick devices can be monitored. By default, jsmond
-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.</p>
-<p>Every <em>interval</em> milliseconds (250, or whatever <strong>-i</strong> is set to), jsmond
-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.</p>
-<p>It's recommended to let jsmond find the joysticks itself. However,
-you can pass one or more device names (or just numbers) if the default
-doesn't do the right thing for you. In this case, only these devices
-will be monitored (no search is done).</p>
-<p>jsmond should be started from your <strong>.xinitrc</strong> or whatever X startup
-script your window manager or desktop environment uses. By default, it
-will exit when the X server does. There's no PID file: use &quot;pkill jsmond&quot;
-if you need to kill the daemon.</p>
-</div>
-<div class="section" id="options">
-<h1>OPTIONS</h1>
-<table class="docutils option-list" frame="void" rules="none">
-<col class="option" />
-<col class="description" />
-<tbody valign="top">
-<tr><td class="option-group">
-<kbd><span class="option">--help</span></kbd></td>
-<td>Print usage summary</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-i <var>&lt;interval&gt;</var></span></kbd></td>
-<td>Interval to check for activity. Can be given in seconds
-with <em>s</em> suffix (e.g. <strong>1s</strong>), or milliseconds with <em>m</em>
-(e.g. <strong>200m</strong>). If just a number is given, it's assumed
-to be in seconds if it's under 100, otherwise it's treated
-as milliseconds. Default: 250m.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-k <var>&lt;keycode&gt;</var></span></kbd></td>
-<td>Send this keycode when activity is detected. Default
-is to search the keymap for an unused code. If you set this
-manually, it should be a keycode that <em>doesn't</em> map to a keysym
-in your usual keymapping (use &quot;xmodmap -pk&quot; to find one).</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-b <var>&lt;button&gt;</var></span></kbd></td>
-<td>Send a click of this button when activity is detected,
-rather than a keystroke. Should be a button that
-applications don't normally respond to (6 or higher),
-but in some environments, the window manager responds to
-all the 'extra' buttons as though they were button 1.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-m</span></kbd></td>
-<td>Send mouse movements rather than a keystroke. This will
-move the pointer 10 pixels to the right and down, then
-10 pixels to the left and up, then warp the pointer back
-to its starting point.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-c <var>&lt;command&gt;</var></span></kbd></td>
-<td>Run a command when activity is detected, rather than
-sending a fake keystroke/click/motion. It's recommended
-to set <em>interval</em> to at least 1 second when using this
-option, to avoid excess process-spawning overhead.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-x</span></kbd></td>
-<td>Same as <strong>-c &quot;xscreensaver-command -deactivate&quot; -i 1s</strong>.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-f</span></kbd></td>
-<td>Deactivate screensaver if a fullscreen window is detected.
-This isn't likely to be 100% reliable yet.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-F</span></kbd></td>
-<td>Same as <strong>-f</strong>, but also disables joystick monitoring entirely.
-Note that <strong>-j</strong>, <strong>-d</strong>, and <strong>joydev</strong> are ignored
-with this option.</td></tr>
-</tbody>
-</table>
-<p>These options are intended for developers and  <em>really</em> shouldn't be
-needed for normal use:</p>
-<table class="docutils option-list" frame="void" rules="none">
-<col class="option" />
-<col class="description" />
-<tbody valign="top">
-<tr><td class="option-group">
-<kbd><span class="option">-d <var>&lt;dir&gt;</var></span></kbd></td>
-<td>Path to the directory containing joystick device nodes.
-Default is &quot;/dev/input&quot;. This directory is monitored with
-inotify(7) so jsmond will be aware of hotplug events.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-j <var>&lt;name&gt;</var></span></kbd></td>
-<td>Name of joystick device nodes, without any numeric
-suffix. Default is &quot;js&quot;.</td></tr>
-<tr><td class="option-group">
-<kbd><span class="option">-D</span></kbd></td>
-<td>Debug mode: run in foreground and print verbose messages.</td></tr>
-</tbody>
-</table>
-<p>A space is required between an option and its argument, as shown
-above. Use e.g. <strong>-i 300</strong>, not <strong>-i300</strong>.</p>
-</div>
-<div class="section" id="notes">
-<h1>NOTES</h1>
-<p>jsmond was tested with xlock(1) and xscreensaver(1). All 3 modes
-(keycode, mouse click, and mouse motion) work with xscreensaver.
-xlock doesn't respond to mouse motion, so use the keycode or click
-modes with it.</p>
-<p>jsmond can monitor up to MAX_STICKS joysticks. This is a compile time
-constant, normally set to 16. See the <strong>--help</strong> output to find out
-the compiled-in default.</p>
-<p><strong>joydev</strong> arguments can be either a path to a device node (e.g.
-<em>/dev/input/js0</em> or similar), or a number, which will have the default
-device basename prepended to it. This is normally &quot;/dev/input/js&quot;, but
-can be changed via the <strong>-d</strong> and <strong>-j</strong> options. Note that (currently)
-all the joystick devices have to be in the same directory for jsmond
-to detect hotplug events!</p>
-<p>Note that it's <em>not</em> an error to give nonexistent joystick device names.
-jsmond will wait for devices to come into existence (e.g. as created
-by <strong>udev</strong>).</p>
-<p>If the screensaver is configured to lock the screen, and it has already
-done so, pressing a joystick button/direction will just bring up the
-password dialog, same as pressing a key or mouse button would.</p>
-<p>jsmond depends on the XTest extension being present in the X server. If
-you get a &quot;X server doesn't support XTest extension&quot; error, see your X
-server documentation to find out how to enable XTest.</p>
-<p>The fullscreen window monitoring has only been tested on a system with
-a single monitor, and may not work properly in multi-head environments.</p>
-</div>
-<div class="section" id="exit-status">
-<h1>EXIT STATUS</h1>
-<p>Without the -D option, the exit status is 0 (success) if jsmond
-successfully forked into the background.</p>
-<p>A non-zero exit status means an error in the command line arguments,
-or else fork() failed. No daemon will be running in this case.</p>
-<p>With the -D option, jsmond never exits until it's killed.</p>
-</div>
-<div class="section" id="bugs">
-<h1>BUGS</h1>
-<p>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
-been plugged in yet. Try to avoid typos, if you really have to use device
-names (better to autodetect).</p>
-<p>Normally once daemonized, jsmond 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?).</p>
-<p>It should be (but currently isn't) possible to at least work in
-mouse-motion mode even without the XTest extension, via XWarpPointer().</p>
-<p>jsmond isn't portable. It only works on Linux, at least for now, for
-three reasons:</p>
-<ul class="simple">
-<li>It uses the Linux joystick API.</li>
-<li>It uses inotify(7) to detect joystick hotplug events.</li>
-<li>I haven't even looked at other OSes to see if it would be possible
-to port the code.</li>
-</ul>
-<!-- EXAMPLES -->
-<!-- ======== -->
-</div>
-<div class="section" id="license">
-<h1>LICENSE</h1>
-<p>jsmond is released under the WTFPL: Do WTF you want with this.</p>
-</div>
-<div class="section" id="author">
-<h1>AUTHOR</h1>
-<p>jsmond was written by B. Watson &lt;<a class="reference external" href="mailto:yalhcru&#64;gmail.com">yalhcru&#64;gmail.com</a>&gt;.</p>
-</div>
-<div class="section" id="see-also">
-<h1>SEE ALSO</h1>
-<p>jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2)</p>
-</div>
-</div>
-</body>
-</html>
diff --git a/jsmond.rst b/jsmond.rst
deleted file mode 100644
index 95f62b9..0000000
--- a/jsmond.rst
+++ /dev/null
@@ -1,195 +0,0 @@
-.. RST source for jsmond(1) man page. Convert with:
-..   rst2man.py jsmond.rst > jsmond.1
-
-.. |version| replace:: 0.2.0
-.. |date| date::
-
-======
-jsmond
-======
-
--------------------------------------------
-deactivate screensaver on joystick activity
--------------------------------------------
-
-:Manual section: 1
-:Manual group: Urchlay
-:Date: |date|
-:Version: |version|
-
-SYNOPSIS
-========
-
-jsmond [**-i interval[s|ms]**] [**-m** | **-k keycode** | **-b button** | **-c command** | **-x** ] [**-d dir**] [**-j name**] [**-f**] [**-F**] [**-D**] [**joydev [joydev ...]**]
-
-DESCRIPTION
-===========
-
-jsmond lets you play games with your joysticks/gamepads without the screen
-saver activating due to lack of keyboard/mouse input. It can also prevent
-the screensaver from activating when a fullscreen window is in use (e.g.
-while watching a movie).
-
-Multiple joystick devices can be monitored. By default, jsmond
-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.
-
-Every *interval* milliseconds (250, or whatever **-i** is set to), jsmond
-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.
-
-It's recommended to let jsmond find the joysticks itself. However,
-you can pass one or more device names (or just numbers) if the default
-doesn't do the right thing for you. In this case, only these devices
-will be monitored (no search is done).
-
-jsmond should be started from your **.xinitrc** or whatever X startup
-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 jsmond"
-if you need to kill the daemon.
-
-OPTIONS
-=======
-
---help         Print usage summary
-
--i <interval>  Interval to check for activity. Can be given in seconds
-               with *s* suffix (e.g. **1s**), or milliseconds with *m*
-               (e.g. **200m**). If just a number is given, it's assumed
-               to be in seconds if it's under 100, otherwise it's treated
-               as milliseconds. Default: 250m.
-
--k <keycode>   Send this keycode when activity is detected. Default
-               is to search the keymap for an unused code. If you set this
-               manually, it should be a keycode that *doesn't* map to a keysym
-               in your usual keymapping (use "xmodmap -pk" to find one).
-
--b <button>    Send a click of this button when activity is detected,
-               rather than a keystroke. Should be a button that
-               applications don't normally respond to (6 or higher),
-               but in some environments, the window manager responds to
-               all the 'extra' buttons as though they were button 1.
-
--m             Send mouse movements rather than a keystroke. This will
-               move the pointer 10 pixels to the right and down, then
-               10 pixels to the left and up, then warp the pointer back
-               to its starting point.
-
--c <command>   Run a command when activity is detected, rather than
-               sending a fake keystroke/click/motion. It's recommended
-               to set *interval* to at least 1 second when using this
-               option, to avoid excess process-spawning overhead.
-
--x             Same as **-c "xscreensaver-command -deactivate" -i 1s**.
-
--f             Deactivate screensaver if a fullscreen window is detected.
-               This isn't likely to be 100% reliable yet.
-
--F             Same as **-f**, but also disables joystick monitoring entirely.
-               Note that **-j**, **-d**, and **joydev** are ignored
-               with this option.
-
-These options are intended for developers and  *really* shouldn't be
-needed for normal use:
-
--d <dir>       Path to the directory containing joystick device nodes.
-               Default is "/dev/input". This directory is monitored with
-               inotify(7) so jsmond will be aware of hotplug events.
-
--j <name>      Name of joystick device nodes, without any numeric
-               suffix. Default is "js".
-
--D             Debug mode: run in foreground and print verbose messages.
-
-A space is required between an option and its argument, as shown
-above. Use e.g. **-i 300**, not **-i300**.
-
-NOTES
-=====
-
-jsmond was tested with xlock(1) and xscreensaver(1). All 3 modes
-(keycode, mouse click, and mouse motion) work with xscreensaver.
-xlock doesn't respond to mouse motion, so use the keycode or click
-modes with it.
-
-jsmond can monitor up to MAX_STICKS joysticks. This is a compile time
-constant, normally set to 16. See the **--help** output to find out
-the compiled-in default.
-
-**joydev** arguments can be either a path to a device node (e.g.
-*/dev/input/js0* or similar), or a number, which will have the default
-device basename prepended to it. This is normally "/dev/input/js", but
-can be changed via the **-d** and **-j** options. Note that (currently)
-all the joystick devices have to be in the same directory for jsmond
-to detect hotplug events!
-
-Note that it's *not* an error to give nonexistent joystick device names.
-jsmond will wait for devices to come into existence (e.g. as created
-by **udev**).
-
-If the screensaver is configured to lock the screen, and it has already
-done so, pressing a joystick button/direction will just bring up the
-password dialog, same as pressing a key or mouse button would.
-
-jsmond depends on the XTest extension being present in the X server. If
-you get a "X server doesn't support XTest extension" error, see your X
-server documentation to find out how to enable XTest.
-
-The fullscreen window monitoring has only been tested on a system with
-a single monitor, and may not work properly in multi-head environments.
-
-EXIT STATUS
-===========
-
-Without the -D option, the exit status is 0 (success) if jsmond
-successfully forked into the background.
-
-A non-zero exit status means an error in the command line arguments,
-or else fork() failed. No daemon will be running in this case.
-
-With the -D option, jsmond never exits until it's killed.
-
-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
-been plugged in yet. Try to avoid typos, if you really have to use device
-names (better to autodetect).
-
-Normally once daemonized, jsmond 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?).
-
-It should be (but currently isn't) possible to at least work in
-mouse-motion mode even without the XTest extension, via XWarpPointer().
-
-jsmond isn't portable. It only works on Linux, at least for now, for
-three reasons:
-
-- It uses the Linux joystick API.
-
-- It uses inotify(7) to detect joystick hotplug events.
-
-- I haven't even looked at other OSes to see if it would be possible
-  to port the code.
-
-.. EXAMPLES
-.. ========
-
-LICENSE
-=======
-
-jsmond is released under the WTFPL: Do WTF you want with this.
-
-AUTHOR
-======
-
-jsmond was written by B. Watson <yalhcru@gmail.com>.
-
-SEE ALSO
-========
-
-jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2)
diff --git a/unsaver.1 b/unsaver.1
new file mode 100644
index 0000000..5a69b40
--- /dev/null
+++ b/unsaver.1
@@ -0,0 +1,216 @@
+.\" Man page generated from reStructuredText.
+.
+.TH UNSAVER 1 "2020-05-19" "0.3.0" "Urchlay"
+.SH NAME
+unsaver \- deactivate screensaver on joystick activity
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.\" RST source for unsaver(1) man page. Convert with:
+.
+.\" rst2man.py unsaver.rst > unsaver.1
+.
+.SH SYNOPSIS
+.sp
+unsaver [\fB\-i interval[s|ms]\fP] [\fB\-m\fP | \fB\-k keycode\fP | \fB\-b button\fP | \fB\-c command\fP | \fB\-x\fP ] [\fB\-d dir\fP] [\fB\-j name\fP] [\fB\-f\fP] [\fB\-F\fP] [\fB\-D\fP] [\fBjoydev [joydev ...]\fP]
+.SH DESCRIPTION
+.sp
+unsaver lets you play games with your joysticks/gamepads without the screen
+saver activating due to lack of keyboard/mouse input. It can also prevent
+the screensaver from activating when a fullscreen window is in use (e.g.
+while watching a movie).
+.sp
+Multiple joystick devices can be monitored. By default, unsaver
+monitors up to 16 devices, named /dev/input/js0 through js15.
+These devices don\(aqt have to actually exist: they can come and go
+as joysticks are plugged in and unplugged.
+.sp
+Every \fIinterval\fP milliseconds (250, or whatever \fB\-i\fP is set to), unsaver
+checks to see if there\(aqs been any activity on any of the devices it\(aqs
+monitoring. If so, it sends a fake mouse movement, keystroke, or mouse
+button click, which the screen saver will see as activity.
+.sp
+It\(aqs recommended to let unsaver find the joysticks itself. However,
+you can pass one or more device names (or just numbers) if the default
+doesn\(aqt do the right thing for you. In this case, only these devices
+will be monitored (no search is done).
+.sp
+unsaver should be started from your \fB\&.xinitrc\fP or whatever X startup
+script your window manager or desktop environment uses. By default, it
+will exit when the X server does. There\(aqs no PID file: use "pkill unsaver"
+if you need to kill the daemon.
+.SH OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-help
+Print usage summary
+.TP
+.BI \-i \ <interval>
+Interval to check for activity. Can be given in seconds
+with \fIs\fP suffix (e.g. \fB1s\fP), or milliseconds with \fIm\fP
+(e.g. \fB200m\fP). If just a number is given, it\(aqs assumed
+to be in seconds if it\(aqs under 100, otherwise it\(aqs treated
+as milliseconds. Default: 250m.
+.TP
+.BI \-k \ <keycode>
+Send this keycode when activity is detected. Default
+is to search the keymap for an unused code. If you set this
+manually, it should be a keycode that \fIdoesn\(aqt\fP map to a keysym
+in your usual keymapping (use "xmodmap \-pk" to find one).
+.TP
+.BI \-b \ <button>
+Send a click of this button when activity is detected,
+rather than a keystroke. Should be a button that
+applications don\(aqt normally respond to (6 or higher),
+but in some environments, the window manager responds to
+all the \(aqextra\(aq buttons as though they were button 1.
+.TP
+.B \-m
+Send mouse movements rather than a keystroke. This will
+move the pointer 10 pixels to the right and down, then
+10 pixels to the left and up, then warp the pointer back
+to its starting point.
+.TP
+.BI \-c \ <command>
+Run a command when activity is detected, rather than
+sending a fake keystroke/click/motion. It\(aqs recommended
+to set \fIinterval\fP to at least 1 second when using this
+option, to avoid excess process\-spawning overhead.
+.TP
+.B \-x
+Same as \fB\-c "xscreensaver\-command \-deactivate" \-i 1s\fP\&.
+.TP
+.B \-f
+Deactivate screensaver if a fullscreen window is detected.
+This isn\(aqt likely to be 100% reliable yet.
+.TP
+.B \-F
+Same as \fB\-f\fP, but also disables joystick monitoring entirely.
+Note that \fB\-j\fP, \fB\-d\fP, and \fBjoydev\fP are ignored
+with this option.
+.UNINDENT
+.sp
+These options are intended for developers and  \fIreally\fP shouldn\(aqt be
+needed for normal use:
+.INDENT 0.0
+.TP
+.BI \-d \ <dir>
+Path to the directory containing joystick device nodes.
+Default is "/dev/input". This directory is monitored with
+inotify(7) so unsaver will be aware of hotplug events.
+.TP
+.BI \-j \ <name>
+Name of joystick device nodes, without any numeric
+suffix. Default is "js".
+.TP
+.B \-D
+Debug mode: run in foreground and print verbose messages.
+.UNINDENT
+.sp
+A space is required between an option and its argument, as shown
+above. Use e.g. \fB\-i 300\fP, not \fB\-i300\fP\&.
+.SH NOTES
+.sp
+unsaver was tested with xlock(1) and xscreensaver(1). All 3 modes
+(keycode, mouse click, and mouse motion) work with xscreensaver.
+xlock doesn\(aqt respond to mouse motion, so use the keycode or click
+modes with it.
+.sp
+unsaver can monitor up to MAX_STICKS joysticks. This is a compile time
+constant, normally set to 16. See the \fB\-\-help\fP output to find out
+the compiled\-in default.
+.sp
+\fBjoydev\fP arguments can be either a path to a device node (e.g.
+\fI/dev/input/js0\fP or similar), or a number, which will have the default
+device basename prepended to it. This is normally "/dev/input/js", but
+can be changed via the \fB\-d\fP and \fB\-j\fP options. Note that (currently)
+all the joystick devices have to be in the same directory for unsaver
+to detect hotplug events!
+.sp
+Note that it\(aqs \fInot\fP an error to give nonexistent joystick device names.
+unsaver will wait for devices to come into existence (e.g. as created
+by \fBudev\fP).
+.sp
+If the screensaver is configured to lock the screen, and it has already
+done so, pressing a joystick button/direction will just bring up the
+password dialog, same as pressing a key or mouse button would.
+.sp
+unsaver depends on the XTest extension being present in the X server. If
+you get a "X server doesn\(aqt support XTest extension" error, see your X
+server documentation to find out how to enable XTest.
+.sp
+The fullscreen window monitoring has only been tested on a system with
+a single monitor, and may not work properly in multi\-head environments.
+.SH EXIT STATUS
+.sp
+Without the \-D option, the exit status is 0 (success) if unsaver
+successfully forked into the background.
+.sp
+A non\-zero exit status means an error in the command line arguments,
+or else fork() failed. No daemon will be running in this case.
+.sp
+With the \-D option, unsaver never exits until it\(aqs killed.
+.SH BUGS
+.sp
+There\(aqs no way to distinguish between an invalid device name and a
+device name that doesn\(aqt happen to exist yet because its device hasn\(aqt
+been plugged in yet. Try to avoid typos, if you really have to use device
+names (better to autodetect).
+.sp
+Normally once daemonized, unsaver is very robust. However, if something
+does go wrong, there\(aqs no way to find out what. Probably there should
+be a log file, or use syslog (or is that overkill?).
+.sp
+It should be (but currently isn\(aqt) possible to at least work in
+mouse\-motion mode even without the XTest extension, via XWarpPointer().
+.sp
+unsaver isn\(aqt portable. It only works on Linux, at least for now, for
+three reasons:
+.INDENT 0.0
+.IP \(bu 2
+It uses the Linux joystick API.
+.IP \(bu 2
+It uses inotify(7) to detect joystick hotplug events.
+.IP \(bu 2
+I haven\(aqt even looked at other OSes to see if it would be possible
+to port the code.
+.UNINDENT
+.\" EXAMPLES
+.
+.\" ========
+.
+.SH LICENSE
+.sp
+unsaver is released under the WTFPL: Do WTF you want with this.
+.SH AUTHOR
+.sp
+unsaver was written by B. Watson <\fI\%yalhcru@gmail.com\fP>.
+.SH SEE ALSO
+.sp
+jstest(1), jscal(1), sdl\-jstest(1), sdl2\-jstest(2)
+.\" Generated by docutils manpage writer.
+.
diff --git a/unsaver.c b/unsaver.c
new file mode 100644
index 0000000..eceb4d3
--- /dev/null
+++ b/unsaver.c
@@ -0,0 +1,754 @@
+/* need this, or else we don't get a prototype for strdup() from string.h */
+#define _XOPEN_SOURCE 500
+
+#include <string.h>
+#include <stdio.h>
+#include <unistd.h>
+#include <stdlib.h>
+#include <sys/types.h>
+#include <sys/stat.h>
+#include <fcntl.h>
+#include <limits.h>
+#include <errno.h>
+
+#include <X11/X.h>
+#include <X11/Xlib.h>
+#include <X11/extensions/XTest.h>
+
+#include <linux/joystick.h>
+#include <sys/inotify.h>
+
+/* microseconds to wait between sending a keypresss
+   or mouse click event and its release */
+#define EVENT_DELAY 100000
+
+/* if we can't find an unused keycode in the X keymap, use this one */
+#define FALLBACK_KEYCODE 255
+
+/* min/max allowed keycodes. really this should be queried from
+   the X server, but for Xorg this value is good enough for
+   argument checking. the max is 0xff as keycodes are 8 bit unsigned. */
+#define MIN_KEYCODE 8
+#define MAX_KEYCODE 255
+
+/* same as above, for mouse buttons. */
+#define MIN_BUTTON 1
+#define MAX_BUTTON 10
+
+/* command for -x */
+#define X_COMMAND "xscreensaver-command -deactivate"
+
+/* default "-i 250ms" */
+#define DEFAULT_INTERVAL 250
+
+typedef enum {
+	fm_auto_keycode, fm_keycode, fm_button, fm_motion, fm_cmd
+} fake_mode_t;
+
+/* user options */
+int interval = DEFAULT_INTERVAL; /* -i (always in millisec) */
+int debug = 0;                   /* -D */
+int keycode = -1;                /* -k */
+int button = -1;                 /* -b */
+char *event_dir = EVENTDIR;      /* -d */
+char *js_node_name = JSNODE;     /* -j */
+int autodiscover = 1; /* cleared if user supplies joydev args */
+fake_mode_t fake_mode = fm_auto_keycode;  /* -k, -b, -m */
+char *c_command = NULL;          /* -c, -x */
+int monitor_joysticks = 1;       /* -F */
+int monitor_fullscreen = 0;      /* -f, -F */
+
+/* joystick stuff */
+char *joynames[MAX_STICKS + 1];
+int last_joyname = 0;
+int joyfds[MAX_STICKS + 1];
+
+/* executable name, for warnings/errors */
+const char *self;
+
+/* X stuff */
+Display *xdisp;
+
+/* inotify stuff */
+int inotify_fd, watch_fd;
+char inotify_buf[sizeof(struct inotify_event) + NAME_MAX + 1];
+struct inotify_event *inotify_ev = (struct inotify_event *)inotify_buf;
+
+/* not going to include pages of usage info duplicating the man page */
+void usage(void) {
+	printf(PROJ " v" VERSION " by B. Watson, WTFPL\n");
+	printf("Usage: %s [-i interval] [-b button | -k keycode] [-j name]\n", self);
+	printf("              [-d dir] [-D] [joystick [...]]\n");
+	printf("Built-in defaults: MAX_STICKS=%d, -d " EVENTDIR ", -j " JSNODE "\n", MAX_STICKS);
+	printf("See man page for details\n");
+	exit(0);
+}
+
+void die(const char *msg) {
+	fprintf(stderr, "%s: %s\n", self, msg);
+	exit(1);
+}
+
+/* make some trivial Xlib call that will result in Xlib killing
+   this process if it fails. XNoOp looks like it was meant for
+   exactly this, but it keeps returning 1 even if the X server is killed. */
+void ping_x_server(void) {
+	(void)XPending(xdisp);
+	if(debug) fprintf(stderr, "X server is still alive\n");
+}
+
+void send_fake_key(void) {
+	if(debug) fprintf(stderr, "sending keycode %d\n", keycode);
+
+	/* press... */
+	XTestFakeKeyEvent(xdisp, keycode, 1, 0L);
+	XSync(xdisp, 0);
+
+	/* ...wait 1/10 sec... */
+	usleep(EVENT_DELAY);
+
+	/* ...release */
+	XTestFakeKeyEvent(xdisp, keycode, 0, 0L);
+	XSync(xdisp, 0);
+}
+
+void send_fake_click(void) {
+	if(debug) fprintf(stderr, "sending button %d click\n", button);
+
+	/* press... */
+	XTestFakeButtonEvent(xdisp, button, 1, 0L);
+	XSync(xdisp, 0);
+
+	/* ...wait 1/10 sec... */
+	usleep(EVENT_DELAY);
+
+	/* ...release */
+	XTestFakeButtonEvent(xdisp, button, 0, 0L);
+	XSync(xdisp, 0);
+}
+
+/* XXX: the man page documents XTestFakeRelativeMotionEvent()
+   as taking 5 arguments (2nd one is screen_number), but Xtst.h
+	only has 4 (with no screen_number arg). */
+void send_fake_motion(void) {
+	int oldx, oldy, ignoreme;
+	Window win_ignoreme;
+
+	if(debug) fprintf(stderr, "sending mouse motion\n");
+
+	XQueryPointer(
+			xdisp,
+			DefaultRootWindow(xdisp),
+			&win_ignoreme,
+			&win_ignoreme,
+			&oldx,
+			&oldy,
+			&ignoreme,
+			&ignoreme,
+			(unsigned int *)&ignoreme);
+
+	if(debug) fprintf(stderr, "oldx %d, oldy %d\n", oldx, oldy);
+
+	/* move... */
+	XTestFakeRelativeMotionEvent(xdisp, 10, 10, 0L);
+	XSync(xdisp, 0);
+
+	/* ...wait 1/10 sec... */
+	usleep(EVENT_DELAY);
+
+	/* ...move back */
+	XTestFakeRelativeMotionEvent(xdisp, -10, -10, 0L);
+	XSync(xdisp, 0);
+
+	/* we've moved all 4 directions now. but if were were too close
+	   to an edge of the screen, the mouse pointer isn't where it
+	   started. so: */
+	XWarpPointer(
+			xdisp,
+			None,
+			DefaultRootWindow(xdisp),
+			0,
+			0,
+			0,
+			0,
+			oldx,
+			oldy);
+	XSync(xdisp, 0);
+}
+
+void exec_command(void) {
+	if(!c_command)
+		die("BUG: c_command is NULL\n");
+
+	if(debug) fprintf(stderr, "executing \"%s\"\n", c_command);
+	system(c_command);
+}
+
+void send_fake_x_event(void) {
+	switch(fake_mode) {
+		case fm_keycode:
+			send_fake_key();
+			break;
+		case fm_button:
+			send_fake_click();
+			break;
+		case fm_motion:
+			send_fake_motion();
+			break;
+		case fm_cmd:
+			exec_command();
+			break;
+		default: /* This Never Happens(tm) */
+			fprintf(stderr, "%s: BUG: fake_mode %d isn't a valid fake_mode_t!\n",
+					self, fake_mode);
+			exit(1);
+			break;
+	}
+}
+
+void open_joysticks(void) {
+	int fdcount, i;
+	struct js_event e;
+
+	fdcount = 0;
+	for(i = 0; i < last_joyname; i++) {
+		int synthev = 0;
+		if(joyfds[i] > -1) close(joyfds[i]);
+		joyfds[i] = open(joynames[i], O_RDONLY | O_NONBLOCK);
+		if(joyfds[i] > -1) {
+			fdcount++;
+			while( (read(joyfds[i], &e, sizeof(e)) > 0) && (e.type & JS_EVENT_INIT) )
+				synthev++;
+			if(debug)
+				fprintf(stderr, "opened %s, fd %d, skipped %d synthetic events\n",
+						joynames[i], joyfds[i], synthev);
+		}
+	}
+	if(debug) fprintf(stderr, "opened %d devices\n", fdcount);
+}
+
+void check_inotify() {
+	int res;
+
+	res = read(inotify_fd, inotify_buf, sizeof(inotify_buf) + NAME_MAX + 1);
+
+	if(res > 0) {
+		if(debug) {
+			fprintf(stderr, "read %d bytes from inotify_fd\n", res);
+			if(!inotify_ev->len) {
+				fprintf(stderr, "got event with no name: 0x%x\n", inotify_ev->mask);
+			} else {
+				fprintf(stderr, "got event with name %s: 0x%x\n", inotify_ev->name, inotify_ev->mask);
+			}
+		}
+
+		/* not much we can do to recover from this: */
+		if(inotify_ev->mask & IN_DELETE_SELF) {
+			die("someone deleted our device directory!");
+		}
+
+		/* ...or this: */
+		if(inotify_ev->mask & IN_UNMOUNT) {
+			die("someone unmounted our device directory!");
+		}
+
+		usleep(EVENT_DELAY); /* might not need, be paranoid */
+		open_joysticks();
+	} else {
+		if(errno != EAGAIN) {
+			/* not sure what could cause this, so no idea how/if we
+			   recover from it */
+			fprintf(stderr, "%s: failed to read from inotify_fd: %s\n",
+					self, strerror(errno));
+			exit(1);
+		}
+	}
+}
+
+int get_joystick_activity(void) {
+	struct js_event e;
+	int i, active = 0;
+
+	for(i = 0; i < last_joyname; i++) {
+		if(joyfds[i] < 0) continue;
+
+		if(debug) fprintf(stderr, "reading device %d, fd %d\n", i, joyfds[i]);
+
+		/* count events. any we get here *should* be real, but it doesn't
+			hurt to mask out synthetic ones again */
+		while(read(joyfds[i], &e, sizeof(e)) > 0) {
+			if(!(e.type & JS_EVENT_INIT)) active++;
+		}
+
+		/* EAGAIN just means there are no more events to read.
+			anything else is a problem, though not fatal */
+		if(errno != EAGAIN) {
+			if(debug) fprintf(stderr, "got error on device %d: %s\n", i, strerror(errno));
+		}
+	}
+
+	return active;
+}
+
+/* supposedly we could use the X window property _NET_WINDOW_FULLSCREEN
+   to detect a fullscreen window, but not everything actually sets that.
+   so a fullscreen window is defined here as:
+   - visible
+   - is the size of the root window
+   - and has input focus.
+*/
+int have_fullscreen_window(void) {
+	Window w;
+	XWindowAttributes w_attrs, root_attrs;
+	int revert_to;
+
+	/* man page doesn't document the actual
+	   return value, it says "int", is it really a Status? */
+	if(!XGetInputFocus(xdisp, &w, &revert_to)) {
+		if(debug) fprintf(stderr, "XGetInputFocus() failed\n");
+		return 0;
+	}
+
+	/* no window has focus (not an error) */
+	if(w == None)
+		return 0;
+
+	/* TODO: under what conditions does this fail? if it does fail once,
+		will it ever succeed again?
+
+		Hopefully, using w_attrs.root will do the right thing in multi-screen
+		environments. I can't easily test it though. */
+	if( XGetWindowAttributes(xdisp, w, &w_attrs) &&
+	    XGetWindowAttributes(xdisp, w_attrs.root, &root_attrs) )
+	{
+
+		if(debug)
+			fprintf(stderr,
+					"window id 0x%x (root 0x%x) has focus, map_state %d, geometry %dx%d\n",
+					(int)w, (int)w_attrs.root, w_attrs.map_state, w_attrs.width, w_attrs.height);
+
+		if( (w_attrs.map_state == IsViewable) &&
+				(root_attrs.width == w_attrs.width) &&
+				(root_attrs.height == w_attrs.height) )
+		{
+			if(debug) fprintf(stderr,
+					"window id 0x%x has input focus and looks fullscreen (%dx%d)\n",
+					(int)w, w_attrs.width, w_attrs.height);
+			return 1;
+		}
+	} else if(debug) {
+		if(debug) fprintf(stderr, "XGetWindowAttributes() failed\n");
+		return 0;
+	}
+
+	return 0;
+}
+
+/* this is the point of no return. the only way out of main_loop()
+   is process death. */
+void main_loop(void) {
+	int sleep_us;
+
+	sleep_us = interval * 1000;
+	fprintf(stderr, "entering main_loop(), sleep_us %d\n", sleep_us);
+
+	while(1) {
+		int active = 0;
+
+		/* Xlib will obligingly kill us, if X goes away */
+		ping_x_server();
+
+		/* check_inotify() will close & reopen the joystick fds as needed */
+		if(monitor_joysticks)
+			check_inotify();
+
+		/* let the fds gather events as we slumber */
+		if(debug) fprintf(stderr, "sleeping %dms...\n", interval);
+		usleep(sleep_us);
+
+		/* now see if any of them got any events while we took a nap */
+		if(monitor_joysticks)
+			active += get_joystick_activity();
+
+		if(monitor_fullscreen)
+			active += have_fullscreen_window();
+
+		/* if we got any activity on any of the fds, do our thing */
+		if(active) {
+			if(debug) fprintf(stderr, "*** got activity!\n");
+			send_fake_x_event();
+		} else if(debug) fprintf(stderr, "no activity\n");
+	}
+}
+
+/* make self point to our executable name without any directory */
+void set_exe_name(const char *argv0) {
+	const char *p;
+	self = argv0;
+	for(p = self; *p; p++)
+		if(p[0] == '/' && p[1]) self = p + 1;
+}
+
+char *make_joystick_name(int js) {
+	static char buf[PATH_MAX + 1];
+	sprintf(buf, "%s/%s%d", event_dir, js_node_name, js);
+	return buf;
+}
+
+/* add a joystick by pathname or number. note this only gets
+   called once, at startup: the list never gets modified after that. */
+void add_joystick_name(const char *name) {
+	if(last_joyname >= MAX_STICKS) {
+		fprintf(stderr,
+				"%s: too many device names, monitoring only the first %d\n",
+				self,
+				last_joyname);
+		return;
+	}
+
+	if(*name >= '0' && *name <= '9') {
+		add_joystick_name(make_joystick_name(atoi(name)));
+		return;
+	}
+
+	if( !(joynames[last_joyname] = strdup(name)) )
+		die(strerror(errno));
+
+	if(debug)
+		fprintf(stderr, "added device name %d: %s\n", last_joyname, name);
+
+	last_joyname++;
+}
+
+void populate_joynames(void) {
+	int i;
+
+	for(i = 0; i < MAX_STICKS; i++) {
+		add_joystick_name(make_joystick_name(i));
+	}
+}
+
+void set_fake_mode(fake_mode_t newmode) {
+	if(fake_mode != fm_auto_keycode)
+		die("use only one of the -k -b -m options");
+	else
+		fake_mode = newmode;
+}
+
+int set_interval(const char *arg) {
+	char *end;
+
+	interval = strtol(arg, &end, 0);
+
+	/* no digits at all */
+	if(end == arg) return 0;
+
+	/* no 0 or negative */
+	if(interval < 1) return 0;
+
+	/* digits only */
+	switch(*end) {
+		case '\0':
+			/* digits only, try to guess */
+			if(interval < 100) {
+				fprintf(stderr,
+						"%s: treating -i %d as %d seconds (use -i %dms if you meant %dms)\n",
+						self, interval, interval, interval, interval);
+				/* fall through */
+			} else {
+				break;
+			}
+		case 's':  interval *= 1000; break; /* sec */
+		case 'm':  break; /* ms, use as-is */
+	}
+
+	if(debug) fprintf(stderr, "interval set to %dms\n", interval);
+	return 1;
+}
+
+void parse_args(int argc, char **argv) {
+	char *nextarg;
+
+	if(argc > 1 && strcmp(argv[1], "--help") == 0) usage();
+
+	while(++argv, --argc) {
+		if(argv[0][0] != '-') {
+			/* no dash, treat as a joystick device */
+			add_joystick_name(*argv);
+			autodiscover = 0;
+		} else {
+			if(argv[0][1] && argv[0][2])
+				die("spaces required between options and arguments, please");
+			nextarg = argv[1];
+			switch(argv[0][1]) {
+				case 'm':
+					set_fake_mode(fm_motion);
+					break;
+				case 'k':
+					if(nextarg &&
+							(keycode = atoi(nextarg)) &&
+							(keycode >= MIN_KEYCODE) &&
+							(keycode <= MAX_KEYCODE) )
+					{
+						set_fake_mode(fm_keycode);
+						argv++, argc--;
+					} else {
+						fprintf(stderr, "%s: -k requires a keycode argument, %d-%d\n",
+								self, MIN_KEYCODE, MAX_KEYCODE);
+						exit(1);
+					}
+					break;
+				case 'b':
+					if(nextarg) button = atoi(nextarg);
+					if ( (button >= MIN_BUTTON) && (button <= MAX_BUTTON) ) {
+						set_fake_mode(fm_button);
+						argv++, argc--;
+					} else {
+						fprintf(stderr, "%s: -b requires a mouse button argument, %d-%d\n",
+								self, MIN_BUTTON, MAX_BUTTON);
+						exit(1);
+					}
+					break;
+				case 'i':
+					if(nextarg && set_interval(nextarg))
+						argv++, argc--;
+					else
+						die("-i requires a positive integer argument in milliseconds");
+					break;
+				case 'd':
+					if(nextarg) {
+						event_dir = nextarg;
+						argv++, argc--;
+					} else {
+						die("-d requires a directory argument");
+					}
+					break;
+				case 'j':
+					if(nextarg) {
+						js_node_name = nextarg;
+						argv++, argc--;
+					} else {
+						die("-j requires a string argument");
+					}
+					break;
+				case 'D':
+					debug = 1;
+					break;
+				case 'c':
+					if(nextarg) {
+						set_fake_mode(fm_cmd);
+						c_command = nextarg;
+						argv++, argc--;
+					} else {
+						die("-c requires a command argument");
+					}
+					break;
+				case 'x':
+					set_fake_mode(fm_cmd);
+					c_command = X_COMMAND;
+					break;
+				case 'F':
+					monitor_joysticks = 0; /* and fall thru */
+				case 'f':
+					monitor_fullscreen = 1;
+					break;
+				default:
+					die("unrecognized argument, try --help");
+					break;
+			}
+		}
+	}
+}
+
+/* make ourselves a daemon, double-fork technique.
+   verbose comments are not here because I think you need them, they're
+   here for me so I don't forget what this gibberish is for... */
+void daemonize(void) {
+	pid_t pid;
+
+	if((pid = fork()) < 0) {
+		/* in parent, fork failed */
+		fprintf(stderr, "%s: %s\n", self, strerror(errno));
+		die("failed to daemonize");
+	} else if(pid) {
+		/* in parent, fork succeeded */
+		exit(0);
+	}
+
+	/* now we're in the child, aka the 2nd generation parent.
+      the only reason for the first fork() was because setsid() can't
+	   be run in the parent process */
+	if( (setsid() < 0) ) {
+		fprintf(stderr, "%s: %s\n", self, strerror(errno));
+		die("failed to daemonize");
+	}
+
+	/* go on, do it again */
+	if((pid = fork()) < 0) {
+		/* in 2nd gen parent, fork failed */
+		fprintf(stderr, "%s: %s\n", self, strerror(errno));
+		die("failed to daemonize");
+	} else if(pid) {
+		/* in 2nd gen parent, fork succeeded */
+		fprintf(stderr, "%s: daemonized, PID %u\n", self, pid);
+		exit(0);
+	}
+
+	/* now we're in the grandchild, and we no longer need stdin/out/err */
+	close(0);
+	close(1);
+	close(2);
+
+	/* do this so we don't keep a filesystem from being umounted because
+		it's still busy (as our cwd) */
+	chdir("/");
+}
+
+/* helpers for init_* functions */
+void connect_to_x(void) {
+	int ignoreme;
+
+	if(debug) fprintf(stderr, "connecting to X server...\n");
+
+	xdisp = XOpenDisplay(getenv("DISPLAY"));
+
+	if(!xdisp) die("can't connect to X server");
+	if(debug) fprintf(stderr, "connected to X server\n");
+
+	if(XTestQueryExtension(xdisp, &ignoreme, &ignoreme, &ignoreme, &ignoreme)) {
+		if(debug) fprintf(stderr, "X server supports XTest extension, good\n");
+	} else {
+		die("X server doesn't support XTest extension\n");
+	}
+}
+
+/* XXX: XKeycodeToKeysym() is deprecated. I must learn XKB. */
+#pragma GCC diagnostic push
+#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
+KeySym get_keysym(int i) {
+	return XKeycodeToKeysym(xdisp, i, 0);
+}
+#pragma GCC diagnostic pop
+
+/* the goggles, they do nothing! */
+void find_keycode() {
+	int i, min_code = 0, max_code = 0;
+	
+	/* man page doesn't document the return value */
+	(void)XDisplayKeycodes(xdisp, &min_code, &max_code);
+
+	if(debug) fprintf(stderr, "XDisplayKeycodes min %d, max %d\n", min_code, max_code);
+
+	for(i = min_code; i <= max_code; i++) {
+		if(get_keysym(i) == NoSymbol) {
+			keycode = i;
+			if(debug) fprintf(stderr, "using keycode %d\n", keycode);
+			break;
+		}
+	}
+
+	if(keycode < 0) {
+		fprintf(stderr,
+				"%s: can't find a free keycode in the keymap, using %d\n",
+				self, FALLBACK_KEYCODE);
+		keycode = FALLBACK_KEYCODE;
+	}
+}
+
+/* the device name check is mostly to guard against typos */
+void check_joyname(int i) {
+	if(joynames[i] && (strncmp(event_dir, joynames[i], strlen(event_dir)) != 0)) {
+		fprintf(stderr, "%s: device %s is not in event dir %s\n",
+				self, joynames[i], event_dir);
+		exit(1);
+	}
+}
+
+/* init_* functions. these are only called once each, from main() */
+void init_joysticks(void) {
+	int i;
+
+	for(i = 0; i < MAX_STICKS; i++) {
+		joyfds[i] = -1;
+		check_joyname(i);
+	}
+
+	open_joysticks();
+}
+
+void init_inotify(void) {
+	inotify_fd = inotify_init1(IN_NONBLOCK);
+	if(inotify_fd < 0) {
+		fprintf(stderr, "%s: inotify_init1() failed: %s",
+				self, strerror(errno));
+		exit(1);
+	}
+
+	if(debug) fprintf(stderr, "inotify_init1() returned %d\n", inotify_fd);
+
+	watch_fd = inotify_add_watch(
+			inotify_fd,
+			event_dir,
+			IN_CREATE | IN_DELETE | IN_DELETE_SELF);
+
+	if(watch_fd < 0) {
+		fprintf(stderr, "%s: inotify_add_watch(\"%s\") failed: %s\n",
+				self, event_dir, strerror(errno));
+		exit(1);
+	}
+
+	if(debug) fprintf(stderr, "inotify_add_watch() on %s returned %d\n", event_dir, inotify_fd);
+}
+
+void init_x(void) {
+	connect_to_x();
+
+	if(fake_mode == fm_auto_keycode) {
+		find_keycode();
+		fake_mode = fm_keycode;
+	}
+
+	/* do this now, before daemonizing. if something's wrong, Xlib
+	   will kill us. we'd better let that happen while we still have a
+	   stderr, so the user can see what happened. */
+	send_fake_x_event();
+}
+
+void print_banner() {
+	const char *m;
+
+	if(monitor_joysticks && monitor_fullscreen) {
+		m = "joysticks and fullscreen";
+	} else if(monitor_joysticks) {
+		m = "joysticks only";
+	} else if(monitor_fullscreen) {
+		m = "fullscreen only";
+	} else {
+		die("nothing to monitor!");
+	}
+
+	fprintf(stderr, "%s: v%s monitoring %s, interval %dms\n",
+			self, VERSION, m, interval);
+}
+
+int main(int argc, char **argv) {
+	set_exe_name(argv[0]);
+
+	parse_args(argc, argv);
+
+	print_banner();
+
+	if(monitor_joysticks) {
+		if(autodiscover) populate_joynames();
+		init_joysticks();
+		init_inotify();
+	}
+
+	init_x();
+
+	if(!debug) daemonize();
+
+	main_loop();
+
+	return 0;
+}
diff --git a/unsaver.html b/unsaver.html
new file mode 100644
index 0000000..7d3ce80
--- /dev/null
+++ b/unsaver.html
@@ -0,0 +1,559 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.14: http://docutils.sourceforge.net/" />
+<title>unsaver</title>
+<meta name="date" content="2020-05-19" />
+<style type="text/css">
+
+/*
+:Author: David Goodger (goodger@python.org)
+:Id: $Id: html4css1.css 7952 2016-07-26 18:15:59Z milde $
+:Copyright: This stylesheet has been placed in the public domain.
+
+Default cascading style sheet for the HTML output of Docutils.
+
+See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
+customize this style sheet.
+*/
+
+/* used to remove borders from tables and images */
+.borderless, table.borderless td, table.borderless th {
+  border: 0 }
+
+table.borderless td, table.borderless th {
+  /* Override padding for "table.docutils td" with "! important".
+     The right padding separates the table cells. */
+  padding: 0 0.5em 0 0 ! important }
+
+.first {
+  /* Override more specific margin styles with "! important". */
+  margin-top: 0 ! important }
+
+.last, .with-subtitle {
+  margin-bottom: 0 ! important }
+
+.hidden {
+  display: none }
+
+.subscript {
+  vertical-align: sub;
+  font-size: smaller }
+
+.superscript {
+  vertical-align: super;
+  font-size: smaller }
+
+a.toc-backref {
+  text-decoration: none ;
+  color: black }
+
+blockquote.epigraph {
+  margin: 2em 5em ; }
+
+dl.docutils dd {
+  margin-bottom: 0.5em }
+
+object[type="image/svg+xml"], object[type="application/x-shockwave-flash"] {
+  overflow: hidden;
+}
+
+/* Uncomment (and remove this text!) to get bold-faced definition list terms
+dl.docutils dt {
+  font-weight: bold }
+*/
+
+div.abstract {
+  margin: 2em 5em }
+
+div.abstract p.topic-title {
+  font-weight: bold ;
+  text-align: center }
+
+div.admonition, div.attention, div.caution, div.danger, div.error,
+div.hint, div.important, div.note, div.tip, div.warning {
+  margin: 2em ;
+  border: medium outset ;
+  padding: 1em }
+
+div.admonition p.admonition-title, div.hint p.admonition-title,
+div.important p.admonition-title, div.note p.admonition-title,
+div.tip p.admonition-title {
+  font-weight: bold ;
+  font-family: sans-serif }
+
+div.attention p.admonition-title, div.caution p.admonition-title,
+div.danger p.admonition-title, div.error p.admonition-title,
+div.warning p.admonition-title, .code .error {
+  color: red ;
+  font-weight: bold ;
+  font-family: sans-serif }
+
+/* Uncomment (and remove this text!) to get reduced vertical space in
+   compound paragraphs.
+div.compound .compound-first, div.compound .compound-middle {
+  margin-bottom: 0.5em }
+
+div.compound .compound-last, div.compound .compound-middle {
+  margin-top: 0.5em }
+*/
+
+div.dedication {
+  margin: 2em 5em ;
+  text-align: center ;
+  font-style: italic }
+
+div.dedication p.topic-title {
+  font-weight: bold ;
+  font-style: normal }
+
+div.figure {
+  margin-left: 2em ;
+  margin-right: 2em }
+
+div.footer, div.header {
+  clear: both;
+  font-size: smaller }
+
+div.line-block {
+  display: block ;
+  margin-top: 1em ;
+  margin-bottom: 1em }
+
+div.line-block div.line-block {
+  margin-top: 0 ;
+  margin-bottom: 0 ;
+  margin-left: 1.5em }
+
+div.sidebar {
+  margin: 0 0 0.5em 1em ;
+  border: medium outset ;
+  padding: 1em ;
+  background-color: #ffffee ;
+  width: 40% ;
+  float: right ;
+  clear: right }
+
+div.sidebar p.rubric {
+  font-family: sans-serif ;
+  font-size: medium }
+
+div.system-messages {
+  margin: 5em }
+
+div.system-messages h1 {
+  color: red }
+
+div.system-message {
+  border: medium outset ;
+  padding: 1em }
+
+div.system-message p.system-message-title {
+  color: red ;
+  font-weight: bold }
+
+div.topic {
+  margin: 2em }
+
+h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
+h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
+  margin-top: 0.4em }
+
+h1.title {
+  text-align: center }
+
+h2.subtitle {
+  text-align: center }
+
+hr.docutils {
+  width: 75% }
+
+img.align-left, .figure.align-left, object.align-left, table.align-left {
+  clear: left ;
+  float: left ;
+  margin-right: 1em }
+
+img.align-right, .figure.align-right, object.align-right, table.align-right {
+  clear: right ;
+  float: right ;
+  margin-left: 1em }
+
+img.align-center, .figure.align-center, object.align-center {
+  display: block;
+  margin-left: auto;
+  margin-right: auto;
+}
+
+table.align-center {
+  margin-left: auto;
+  margin-right: auto;
+}
+
+.align-left {
+  text-align: left }
+
+.align-center {
+  clear: both ;
+  text-align: center }
+
+.align-right {
+  text-align: right }
+
+/* reset inner alignment in figures */
+div.align-right {
+  text-align: inherit }
+
+/* div.align-center * { */
+/*   text-align: left } */
+
+.align-top    {
+  vertical-align: top }
+
+.align-middle {
+  vertical-align: middle }
+
+.align-bottom {
+  vertical-align: bottom }
+
+ol.simple, ul.simple {
+  margin-bottom: 1em }
+
+ol.arabic {
+  list-style: decimal }
+
+ol.loweralpha {
+  list-style: lower-alpha }
+
+ol.upperalpha {
+  list-style: upper-alpha }
+
+ol.lowerroman {
+  list-style: lower-roman }
+
+ol.upperroman {
+  list-style: upper-roman }
+
+p.attribution {
+  text-align: right ;
+  margin-left: 50% }
+
+p.caption {
+  font-style: italic }
+
+p.credits {
+  font-style: italic ;
+  font-size: smaller }
+
+p.label {
+  white-space: nowrap }
+
+p.rubric {
+  font-weight: bold ;
+  font-size: larger ;
+  color: maroon ;
+  text-align: center }
+
+p.sidebar-title {
+  font-family: sans-serif ;
+  font-weight: bold ;
+  font-size: larger }
+
+p.sidebar-subtitle {
+  font-family: sans-serif ;
+  font-weight: bold }
+
+p.topic-title {
+  font-weight: bold }
+
+pre.address {
+  margin-bottom: 0 ;
+  margin-top: 0 ;
+  font: inherit }
+
+pre.literal-block, pre.doctest-block, pre.math, pre.code {
+  margin-left: 2em ;
+  margin-right: 2em }
+
+pre.code .ln { color: grey; } /* line numbers */
+pre.code, code { background-color: #eeeeee }
+pre.code .comment, code .comment { color: #5C6576 }
+pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
+pre.code .literal.string, code .literal.string { color: #0C5404 }
+pre.code .name.builtin, code .name.builtin { color: #352B84 }
+pre.code .deleted, code .deleted { background-color: #DEB0A1}
+pre.code .inserted, code .inserted { background-color: #A3D289}
+
+span.classifier {
+  font-family: sans-serif ;
+  font-style: oblique }
+
+span.classifier-delimiter {
+  font-family: sans-serif ;
+  font-weight: bold }
+
+span.interpreted {
+  font-family: sans-serif }
+
+span.option {
+  white-space: nowrap }
+
+span.pre {
+  white-space: pre }
+
+span.problematic {
+  color: red }
+
+span.section-subtitle {
+  /* font-size relative to parent (h1..h6 element) */
+  font-size: 80% }
+
+table.citation {
+  border-left: solid 1px gray;
+  margin-left: 1px }
+
+table.docinfo {
+  margin: 2em 4em }
+
+table.docutils {
+  margin-top: 0.5em ;
+  margin-bottom: 0.5em }
+
+table.footnote {
+  border-left: solid 1px black;
+  margin-left: 1px }
+
+table.docutils td, table.docutils th,
+table.docinfo td, table.docinfo th {
+  padding-left: 0.5em ;
+  padding-right: 0.5em ;
+  vertical-align: top }
+
+table.docutils th.field-name, table.docinfo th.docinfo-name {
+  font-weight: bold ;
+  text-align: left ;
+  white-space: nowrap ;
+  padding-left: 0 }
+
+/* "booktabs" style (no vertical lines) */
+table.docutils.booktabs {
+  border: 0px;
+  border-top: 2px solid;
+  border-bottom: 2px solid;
+  border-collapse: collapse;
+}
+table.docutils.booktabs * {
+  border: 0px;
+}
+table.docutils.booktabs th {
+  border-bottom: thin solid;
+  text-align: left;
+}
+
+h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
+h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
+  font-size: 100% }
+
+ul.auto-toc {
+  list-style-type: none }
+
+</style>
+</head>
+<body>
+<div class="document" id="unsaver">
+<h1 class="title">unsaver</h1>
+<h2 class="subtitle" id="deactivate-screensaver-on-joystick-activity">deactivate screensaver on joystick activity</h2>
+<table class="docinfo" frame="void" rules="none">
+<col class="docinfo-name" />
+<col class="docinfo-content" />
+<tbody valign="top">
+<tr class="manual-section field"><th class="docinfo-name">Manual section:</th><td class="field-body">1</td>
+</tr>
+<tr class="manual-group field"><th class="docinfo-name">Manual group:</th><td class="field-body">Urchlay</td>
+</tr>
+<tr><th class="docinfo-name">Date:</th>
+<td>2020-05-19</td></tr>
+<tr><th class="docinfo-name">Version:</th>
+<td>0.3.0</td></tr>
+</tbody>
+</table>
+<!-- RST source for unsaver(1) man page. Convert with: -->
+<!-- rst2man.py unsaver.rst > unsaver.1 -->
+<div class="section" id="synopsis">
+<h1>SYNOPSIS</h1>
+<p>unsaver [<strong>-i interval[s|ms]</strong>] [<strong>-m</strong> | <strong>-k keycode</strong> | <strong>-b button</strong> | <strong>-c command</strong> | <strong>-x</strong> ] [<strong>-d dir</strong>] [<strong>-j name</strong>] [<strong>-f</strong>] [<strong>-F</strong>] [<strong>-D</strong>] [<strong>joydev [joydev ...]</strong>]</p>
+</div>
+<div class="section" id="description">
+<h1>DESCRIPTION</h1>
+<p>unsaver lets you play games with your joysticks/gamepads without the screen
+saver activating due to lack of keyboard/mouse input. It can also prevent
+the screensaver from activating when a fullscreen window is in use (e.g.
+while watching a movie).</p>
+<p>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.</p>
+<p>Every <em>interval</em> milliseconds (250, or whatever <strong>-i</strong> 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.</p>
+<p>It's recommended to let unsaver find the joysticks itself. However,
+you can pass one or more device names (or just numbers) if the default
+doesn't do the right thing for you. In this case, only these devices
+will be monitored (no search is done).</p>
+<p>unsaver should be started from your <strong>.xinitrc</strong> or whatever X startup
+script your window manager or desktop environment uses. By default, it
+will exit when the X server does. There's no PID file: use &quot;pkill unsaver&quot;
+if you need to kill the daemon.</p>
+</div>
+<div class="section" id="options">
+<h1>OPTIONS</h1>
+<table class="docutils option-list" frame="void" rules="none">
+<col class="option" />
+<col class="description" />
+<tbody valign="top">
+<tr><td class="option-group">
+<kbd><span class="option">--help</span></kbd></td>
+<td>Print usage summary</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-i <var>&lt;interval&gt;</var></span></kbd></td>
+<td>Interval to check for activity. Can be given in seconds
+with <em>s</em> suffix (e.g. <strong>1s</strong>), or milliseconds with <em>m</em>
+(e.g. <strong>200m</strong>). If just a number is given, it's assumed
+to be in seconds if it's under 100, otherwise it's treated
+as milliseconds. Default: 250m.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-k <var>&lt;keycode&gt;</var></span></kbd></td>
+<td>Send this keycode when activity is detected. Default
+is to search the keymap for an unused code. If you set this
+manually, it should be a keycode that <em>doesn't</em> map to a keysym
+in your usual keymapping (use &quot;xmodmap -pk&quot; to find one).</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-b <var>&lt;button&gt;</var></span></kbd></td>
+<td>Send a click of this button when activity is detected,
+rather than a keystroke. Should be a button that
+applications don't normally respond to (6 or higher),
+but in some environments, the window manager responds to
+all the 'extra' buttons as though they were button 1.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-m</span></kbd></td>
+<td>Send mouse movements rather than a keystroke. This will
+move the pointer 10 pixels to the right and down, then
+10 pixels to the left and up, then warp the pointer back
+to its starting point.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-c <var>&lt;command&gt;</var></span></kbd></td>
+<td>Run a command when activity is detected, rather than
+sending a fake keystroke/click/motion. It's recommended
+to set <em>interval</em> to at least 1 second when using this
+option, to avoid excess process-spawning overhead.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-x</span></kbd></td>
+<td>Same as <strong>-c &quot;xscreensaver-command -deactivate&quot; -i 1s</strong>.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-f</span></kbd></td>
+<td>Deactivate screensaver if a fullscreen window is detected.
+This isn't likely to be 100% reliable yet.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-F</span></kbd></td>
+<td>Same as <strong>-f</strong>, but also disables joystick monitoring entirely.
+Note that <strong>-j</strong>, <strong>-d</strong>, and <strong>joydev</strong> are ignored
+with this option.</td></tr>
+</tbody>
+</table>
+<p>These options are intended for developers and  <em>really</em> shouldn't be
+needed for normal use:</p>
+<table class="docutils option-list" frame="void" rules="none">
+<col class="option" />
+<col class="description" />
+<tbody valign="top">
+<tr><td class="option-group">
+<kbd><span class="option">-d <var>&lt;dir&gt;</var></span></kbd></td>
+<td>Path to the directory containing joystick device nodes.
+Default is &quot;/dev/input&quot;. This directory is monitored with
+inotify(7) so unsaver will be aware of hotplug events.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-j <var>&lt;name&gt;</var></span></kbd></td>
+<td>Name of joystick device nodes, without any numeric
+suffix. Default is &quot;js&quot;.</td></tr>
+<tr><td class="option-group">
+<kbd><span class="option">-D</span></kbd></td>
+<td>Debug mode: run in foreground and print verbose messages.</td></tr>
+</tbody>
+</table>
+<p>A space is required between an option and its argument, as shown
+above. Use e.g. <strong>-i 300</strong>, not <strong>-i300</strong>.</p>
+</div>
+<div class="section" id="notes">
+<h1>NOTES</h1>
+<p>unsaver was tested with xlock(1) and xscreensaver(1). All 3 modes
+(keycode, mouse click, and mouse motion) work with xscreensaver.
+xlock doesn't respond to mouse motion, so use the keycode or click
+modes with it.</p>
+<p>unsaver can monitor up to MAX_STICKS joysticks. This is a compile time
+constant, normally set to 16. See the <strong>--help</strong> output to find out
+the compiled-in default.</p>
+<p><strong>joydev</strong> arguments can be either a path to a device node (e.g.
+<em>/dev/input/js0</em> or similar), or a number, which will have the default
+device basename prepended to it. This is normally &quot;/dev/input/js&quot;, but
+can be changed via the <strong>-d</strong> and <strong>-j</strong> options. Note that (currently)
+all the joystick devices have to be in the same directory for unsaver
+to detect hotplug events!</p>
+<p>Note that it's <em>not</em> an error to give nonexistent joystick device names.
+unsaver will wait for devices to come into existence (e.g. as created
+by <strong>udev</strong>).</p>
+<p>If the screensaver is configured to lock the screen, and it has already
+done so, pressing a joystick button/direction will just bring up the
+password dialog, same as pressing a key or mouse button would.</p>
+<p>unsaver depends on the XTest extension being present in the X server. If
+you get a &quot;X server doesn't support XTest extension&quot; error, see your X
+server documentation to find out how to enable XTest.</p>
+<p>The fullscreen window monitoring has only been tested on a system with
+a single monitor, and may not work properly in multi-head environments.</p>
+</div>
+<div class="section" id="exit-status">
+<h1>EXIT STATUS</h1>
+<p>Without the -D option, the exit status is 0 (success) if unsaver
+successfully forked into the background.</p>
+<p>A non-zero exit status means an error in the command line arguments,
+or else fork() failed. No daemon will be running in this case.</p>
+<p>With the -D option, unsaver never exits until it's killed.</p>
+</div>
+<div class="section" id="bugs">
+<h1>BUGS</h1>
+<p>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
+been plugged in yet. Try to avoid typos, if you really have to use device
+names (better to autodetect).</p>
+<p>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?).</p>
+<p>It should be (but currently isn't) possible to at least work in
+mouse-motion mode even without the XTest extension, via XWarpPointer().</p>
+<p>unsaver isn't portable. It only works on Linux, at least for now, for
+three reasons:</p>
+<ul class="simple">
+<li>It uses the Linux joystick API.</li>
+<li>It uses inotify(7) to detect joystick hotplug events.</li>
+<li>I haven't even looked at other OSes to see if it would be possible
+to port the code.</li>
+</ul>
+<!-- EXAMPLES -->
+<!-- ======== -->
+</div>
+<div class="section" id="license">
+<h1>LICENSE</h1>
+<p>unsaver is released under the WTFPL: Do WTF you want with this.</p>
+</div>
+<div class="section" id="author">
+<h1>AUTHOR</h1>
+<p>unsaver was written by B. Watson &lt;<a class="reference external" href="mailto:yalhcru&#64;gmail.com">yalhcru&#64;gmail.com</a>&gt;.</p>
+</div>
+<div class="section" id="see-also">
+<h1>SEE ALSO</h1>
+<p>jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2)</p>
+</div>
+</div>
+</body>
+</html>
diff --git a/unsaver.rst b/unsaver.rst
new file mode 100644
index 0000000..6e6f1dd
--- /dev/null
+++ b/unsaver.rst
@@ -0,0 +1,195 @@
+.. RST source for unsaver(1) man page. Convert with:
+..   rst2man.py unsaver.rst > unsaver.1
+
+.. |version| replace:: 0.3.0
+.. |date| date::
+
+=======
+unsaver
+=======
+
+-------------------------------------------
+deactivate screensaver on joystick activity
+-------------------------------------------
+
+:Manual section: 1
+:Manual group: Urchlay
+:Date: |date|
+:Version: |version|
+
+SYNOPSIS
+========
+
+unsaver [**-i interval[s|ms]**] [**-m** | **-k keycode** | **-b button** | **-c command** | **-x** ] [**-d dir**] [**-j name**] [**-f**] [**-F**] [**-D**] [**joydev [joydev ...]**]
+
+DESCRIPTION
+===========
+
+unsaver lets you play games with your joysticks/gamepads without the screen
+saver activating due to lack of keyboard/mouse input. It can also prevent
+the screensaver from activating when a fullscreen window is in use (e.g.
+while watching a movie).
+
+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.
+
+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.
+
+It's recommended to let unsaver find the joysticks itself. However,
+you can pass one or more device names (or just numbers) if the default
+doesn't do the right thing for you. In this case, only these devices
+will be monitored (no search is done).
+
+unsaver should be started from your **.xinitrc** or whatever X startup
+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.
+
+OPTIONS
+=======
+
+--help         Print usage summary
+
+-i <interval>  Interval to check for activity. Can be given in seconds
+               with *s* suffix (e.g. **1s**), or milliseconds with *m*
+               (e.g. **200m**). If just a number is given, it's assumed
+               to be in seconds if it's under 100, otherwise it's treated
+               as milliseconds. Default: 250m.
+
+-k <keycode>   Send this keycode when activity is detected. Default
+               is to search the keymap for an unused code. If you set this
+               manually, it should be a keycode that *doesn't* map to a keysym
+               in your usual keymapping (use "xmodmap -pk" to find one).
+
+-b <button>    Send a click of this button when activity is detected,
+               rather than a keystroke. Should be a button that
+               applications don't normally respond to (6 or higher),
+               but in some environments, the window manager responds to
+               all the 'extra' buttons as though they were button 1.
+
+-m             Send mouse movements rather than a keystroke. This will
+               move the pointer 10 pixels to the right and down, then
+               10 pixels to the left and up, then warp the pointer back
+               to its starting point.
+
+-c <command>   Run a command when activity is detected, rather than
+               sending a fake keystroke/click/motion. It's recommended
+               to set *interval* to at least 1 second when using this
+               option, to avoid excess process-spawning overhead.
+
+-x             Same as **-c "xscreensaver-command -deactivate" -i 1s**.
+
+-f             Deactivate screensaver if a fullscreen window is detected.
+               This isn't likely to be 100% reliable yet.
+
+-F             Same as **-f**, but also disables joystick monitoring entirely.
+               Note that **-j**, **-d**, and **joydev** are ignored
+               with this option.
+
+These options are intended for developers and  *really* shouldn't be
+needed for normal use:
+
+-d <dir>       Path to the directory containing joystick device nodes.
+               Default is "/dev/input". This directory is monitored with
+               inotify(7) so unsaver will be aware of hotplug events.
+
+-j <name>      Name of joystick device nodes, without any numeric
+               suffix. Default is "js".
+
+-D             Debug mode: run in foreground and print verbose messages.
+
+A space is required between an option and its argument, as shown
+above. Use e.g. **-i 300**, not **-i300**.
+
+NOTES
+=====
+
+unsaver was tested with xlock(1) and xscreensaver(1). All 3 modes
+(keycode, mouse click, and mouse motion) work with xscreensaver.
+xlock doesn't respond to mouse motion, so use the keycode or click
+modes with it.
+
+unsaver can monitor up to MAX_STICKS joysticks. This is a compile time
+constant, normally set to 16. See the **--help** output to find out
+the compiled-in default.
+
+**joydev** arguments can be either a path to a device node (e.g.
+*/dev/input/js0* or similar), or a number, which will have the default
+device basename prepended to it. This is normally "/dev/input/js", but
+can be changed via the **-d** and **-j** options. Note that (currently)
+all the joystick devices have to be in the same directory for unsaver
+to detect hotplug events!
+
+Note that it's *not* an error to give nonexistent joystick device names.
+unsaver will wait for devices to come into existence (e.g. as created
+by **udev**).
+
+If the screensaver is configured to lock the screen, and it has already
+done so, pressing a joystick button/direction will just bring up the
+password dialog, same as pressing a key or mouse button would.
+
+unsaver depends on the XTest extension being present in the X server. If
+you get a "X server doesn't support XTest extension" error, see your X
+server documentation to find out how to enable XTest.
+
+The fullscreen window monitoring has only been tested on a system with
+a single monitor, and may not work properly in multi-head environments.
+
+EXIT STATUS
+===========
+
+Without the -D option, the exit status is 0 (success) if unsaver
+successfully forked into the background.
+
+A non-zero exit status means an error in the command line arguments,
+or else fork() failed. No daemon will be running in this case.
+
+With the -D option, unsaver never exits until it's killed.
+
+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
+been plugged in yet. Try to avoid typos, if you really have to use device
+names (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?).
+
+It should be (but currently isn't) possible to at least work in
+mouse-motion mode even without the XTest extension, via XWarpPointer().
+
+unsaver isn't portable. It only works on Linux, at least for now, for
+three reasons:
+
+- It uses the Linux joystick API.
+
+- It uses inotify(7) to detect joystick hotplug events.
+
+- I haven't even looked at other OSes to see if it would be possible
+  to port the code.
+
+.. EXAMPLES
+.. ========
+
+LICENSE
+=======
+
+unsaver is released under the WTFPL: Do WTF you want with this.
+
+AUTHOR
+======
+
+unsaver was written by B. Watson <yalhcru@gmail.com>.
+
+SEE ALSO
+========
+
+jstest(1), jscal(1), sdl-jstest(1), sdl2-jstest(2)
-- 
cgit v1.2.3