[7132] in SIPB bug reports
Re: xidle
daemon@ATHENA.MIT.EDU (James M. Kretchmar)
Mon Jan 11 11:53:46 1999
To: Sam Hartman <hartmans@MIT.EDU>
Cc: "James M. Kretchmar" <kretch@MIT.EDU>, bug-sipb@MIT.EDU
In-Reply-To: Your message of "11 Jan 1999 11:25:14 EST."
<tslvhidg4k5.fsf@luminous.mit.edu>
Date: Mon, 11 Jan 1999 11:53:40 EST
From: "James M. Kretchmar" <kretch@MIT.EDU>
> Have you already compared to xautolock?
Didn't know about xautolock, but I've looked at it now. There are
some things I don't like about it, but it did get at least one thing
right that I didn't think of.
I'll play with it and either install that instead of xidle, or else
grab what i like from xautolock and put it in xidle.
btw, for the curious, things i don't like about xautolock include:
- can only specify timeout as accurate as minutes
- the timer restarts when the command run on timeout exits (this sucks
if I just want to get a zephyr that I'm idle or something)
- the README and manpage indicate some shoddy timing stuff in more
than one place
- the corners stuff is a mess
- in the near future xidle will also fail to timeout if it gets mouse
click events, xautolock doesn't do that. (nice for web browsing!)
Things I do like about xautolock:
- it pays attention to windows created after its instantiation. I
forgot to do that.
- it lets you do a 'warning' type command before the main command is
executed
- it bothered with Xresources, i should do that
kretch
