On Wed, Sep 25, 2002 at 06:40:03PM -0400, Josh Rollyson wrote: > In reality, the behavior of auto_unmark_away could be easily handled by > a script, easily allowing the client to support both behaviors.
Indeed. Writing a script to provide this functionality is extremely basic. It need only consist of a global variable to keep track of a timestamp for last input and a single /ON INPUT hook to update this global variable and, when necessary, unset away. The following is taken from my away module that is included with the DarkStar script pack (http://darkstar.epicsol.org/). As you can see, it is pretty simple. @ AWAY.LAST_INPUT = time() on #-input 421 "*" { @ AWAY.LAST_INPUT = time() if (A && CONFIG.AUTO_UNSET_AWAY) { //away -a } } > So, which is better? Changing the code to match the documentation, > changing the documentation to match the code, or removing > auto_unmark_away altogether, and including a script with the client to > provide the same function? > > Any comments on the matter would be greatly appreciated. > > -dracus Given the ease with which this feature can be reproduced, I think it would probably be best to simply remove it from the client and include a script that provides the same functionality. The only reason I see to have it builtin is for the sake of convenience. The question is, is this convenience worth it? Cheers, Brian
msg00222/pgp00000.pgp
Description: PGP signature
