(and other) operations.  This should allow fixing the mouse flickering in
SyncTERM on Nokia N800/N900 devices.

I can't remember why the mouse pointer is turned off to be honest...

path.

Thanks!

are where the code was actually "wrong" in some way and the cast was not
intentional.

If the compiler thinks you need to be warned about casting a pointer to an
int of a different size and that's exactly what we mean to do, then we
*should* be getting a warning.

problem and kill it once and for all by doing terrible terrible things.

Essentially, the problem stems from SDL installing an atexit() handler and
cryptlib calling exit() after a fork().  This causes the child to attempt
to shut down SDL (which isn't running in the child) which apparently spins.

I've "fixed" this by overriding exit()!!!  So any exit() call will not call
atexit() functions from SyncTERM anymore.

I haven't yet decided if this is a cryptlib bug or an SDL bug, though I'm
leaning toward SDL.

Reported by Aapo Rantalainen (Thanks!)

Nokia N900.

Debugged and initial patch by Aapo Rantalainen (Thanks!)

XSelectionEvent.property is zero.

Debugged and patched by Marcin Cieslak (aka Saper) in SDL output.  Same patch
applied to X11 output.

Thanks!

Added --retry to enable 5 minute timeout on "stop" and "restart" commands.
Updated comments.
Added 'ulimit -c' line to enable core dumps (commented out).

the request is closed).

* Concatenate various MODULE commands into one bigger command.
* PARTCHAN and JOINCHAN now just "PART" and "JOIN"
* Irrlevant cosmetic fixes and CVS pollution.

a zero-length one).

This fixes the problem everyone but me has known about for some time now.

too complicated for me to be comfortable supporting. if anyone still would like a copy email me, but i think the better idea is for them to make their own, to their needs.

acknowledgement ("250 OK") can be sent. In this case, the sender is either a
spammer or it is a legitimate delivery attempt that has been aborted for some
reason (e.g. timeout due to throttling).

of two.

Essentially, any bits above the next lowest power of two are less likely
to be set.  For example, xp_random(6) would use 3 bits of randomness with
the following distribution:

000 = 0
001 = 1
010 = 2
011 = 3
100 = 4
101 = 5
110 = 0
111 = 1

As you can see, zero and one are twice as likely to occur than 2,3,4, or 5.

around C++ scoping issues (return from a macro?). :-)

Updated copyright dates.

make system.matchuserdata return only the next match (instead of all matches) from specified starting user if match_next==true. add system.matchallusers(field,data); to return an array containing all matches.

user.dat record offset.

descriptor (-1), this is part of the node.dab error recovery scheme.

make system.matchuserdata return an array of all matches if match_all==true, starting at usernumber if specified. (userdatdupe now takes an additional paremeter)

command, where end of article range was not provided (or provided as 0).
Patch by Ragnarok.