From e29c982243f4d1201e93ad3afcfafbf1ee7c3f25 Mon Sep 17 00:00:00 2001 From: "B. Watson" Date: Sat, 23 May 2020 01:51:39 -0400 Subject: use XKB extension instead of deprecated API --- unsaver.1 | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'unsaver.1') diff --git a/unsaver.1 b/unsaver.1 index 5fcf97a..623a291 100644 --- a/unsaver.1 +++ b/unsaver.1 @@ -1,6 +1,6 @@ .\" Man page generated from reStructuredText. . -.TH UNSAVER 1 "2020-05-20" "0.3.0" "Urchlay" +.TH UNSAVER 1 "2020-05-23" "0.4.0" "Urchlay" .SH NAME unsaver \- deactivate screensaver on joystick activity . @@ -102,6 +102,7 @@ Only one of \fB\-k\fP/\fB\-b\fP/\fB\-m\fP/\fB\-c\fP/\fB\-x\fP is accepted. .TP .BI \-k \ Send this keycode when activity is detected. Default +(with no \fB\-k\fP/\fB\-b\fP/\fB\-m\fP/\fB\-c\fP/\fB\-x\fP options) 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). @@ -202,15 +203,12 @@ numbers (it\(aqs 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?). +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. .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 -I \fIreally\fP need to use the XKB extension rather than the old & deprecated -Xlib keyboard API. This mainly affects the default "find an unused -keycode" mode. -.sp unsaver isn\(aqt portable. It only works on Linux, at least for now, for three reasons: .INDENT 0.0 -- cgit v1.2.3