	For the most part autostatus is "right" from the time you install imcom
- after 10 minutes it'll set your status to away, and after 20 minutes
it'll set your status to xa. When you do anything that involves
communicating with someone (or just enter a blank line) it brings you
back to online. This is about what you'd expect from, say, micq.

	These instructions are for more advanced ways of using autostatus
(the reason why it's called autostatus and not autoaway, really).

	We'll start with the default autostatus settings that you're given when
you first setup imcom (note that if you already have an imcomrc you don't
have these settings and will need to add them by hand into your <profile>
tag if you want them).

    <autostatus>
      <status current='online' auto='all' idle='10' new='away' >Auto-away after 10 minutes</status>
      <status current='away' auto='auto' idle='20' new='xa' >Auto-away after 20 minutes</status>
      <status current='away,xa' auto='auto' idle='0' new='online' ></status>
    </autostatus>

	The first rule works at any time (more on that later) and only
triggers if your status is online, your status was set either
automatically or with the /away command, and your idle time is 10 minutes
(exactly). When it triggers it sets your status to away with the message
"Auto-away after 10 minutes"

	The second should be self-explanatory except that it only triggers if
your status of away was set by autostatus and not with the /away command.

	The third triggers if your current status is either away or xa (set
automatically) and brings you back online.

	The available items to match are:

time -     expressed as a range, in military time (e.g. 03:45-14:30 for 
           3:45am to 2:30pm). defaults to any time
current -  current status; defaults to "all"
auto -     auto for current status was set by autostatus, manual for current
           status was set by the user; defaults to "all" 
idle -     number of minutes idle. no default (must be specified).
new -      status to change to. no default (must be specified). it's
           not really used in matching :) but it fits here.

There are a few current caveats that will hopefully be fixed soon :)

1) the rules are evaluated in order - if multiple rules match the current
situation then the one that came first in the config file wins. This will
be changed in the future to a "best-fit" matching scheme, where the most
specific (that is, restrictive) match wins.

2) times currently can't span midnight :) so if you have a "i must be
awake coding thanks to jolt" rule you'll need to break it into two rules
- one that ends at 23:59 and one that starts at 00:00.
 
Examples:

One for your co-workers - between 8:30am and 4:30pm make sure they all
know that you're still working, even if you don't happen to be answering :)
      <status time='08:30-16:30' current='online' auto='all' idle='10' new='away'>Working, promise :)</status>

And for those nights that you fell asleep coding while waiting for someone 
to reply to you:
      <status time='00:00-08:29' current='online' auto='all' idle='20' new='xa' >Probably sleeping</status>
 

