aboutsummaryrefslogtreecommitdiff
path: root/unsaver.rst
diff options
context:
space:
mode:
Diffstat (limited to 'unsaver.rst')
-rw-r--r--unsaver.rst10
1 files changed, 4 insertions, 6 deletions
diff --git a/unsaver.rst b/unsaver.rst
index 734d828..dc05f44 100644
--- a/unsaver.rst
+++ b/unsaver.rst
@@ -1,7 +1,7 @@
.. RST source for unsaver(1) man page. Convert with:
.. rst2man.py unsaver.rst > unsaver.1
-.. |version| replace:: 0.3.0
+.. |version| replace:: 0.4.0
.. |date| date::
=======
@@ -85,6 +85,7 @@ Deactivation mode options
Only one of **-k**/**-b**/**-m**/**-c**/**-x** is accepted.
-k <keycode> Send this keycode when activity is detected. Default
+ (with no **-k**/**-b**/**-m**/**-c**/**-x** options)
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).
@@ -188,15 +189,12 @@ numbers (it's better to autodetect).
Normally once daemonized, unsaver is very robust. However, if something
does go wrong, there's no way to find out what. Probably there should
-be a log file, or use syslog (or is that overkill?).
+be a log file, or use syslog (or is that overkill?). The best you can
+do for now is run it with -d and maybe redirect stderr to a log file.
It should be (but currently isn't) possible to at least work in
mouse-motion mode even without the XTest extension, via XWarpPointer().
-I *really* need to use the XKB extension rather than the old & deprecated
-Xlib keyboard API. This mainly affects the default "find an unused
-keycode" mode.
-
unsaver isn't portable. It only works on Linux, at least for now, for
three reasons: