irctk

libircclient binding for scripts
git clone https://a3nm.net/git/irctk/
Log | Files | Refs | README

commit 73874547840188d67769cc4152dd4d81d333183d
parent a4077c8e82d238b491b820b263d3c732cc3c2ddf
Author: Antoine Amarilli <a3nm@a3nm.net>
Date:   Fri,  9 May 2014 19:06:03 +0200

gender-neutral

Diffstat:
README | 12++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README b/README @@ -378,12 +378,12 @@ correctly. As a countermeasure, you can specify --track-renames so that messages addressed to a user in one of the above fashions get sent to the user's current nick. -(They will get sent to his last known nick if he parts or quits.) There is also -a --unique-names options with which irctk will maintain unique names for users -(based on the first seen nick for a user), expose them on stdout, and expect -them on stdin. This is useful if you want to write a bot which stores e.g. a -score for each user and if you want users to keep their score even if they -change nick. These tracking modes are not enabled by default. +(They will get sent to their last known nick if they part or quit.) There is +also a --unique-names options with which irctk will maintain unique names for +users (based on the first seen nick for a user), expose them on stdout, and +expect them on stdin. This is useful if you want to write a bot which stores +e.g. a score for each user and if you want users to keep their score even if +they change nick. These tracking modes are not enabled by default. === 3.9. Pipelining ===