diff options
author | Luke Bratch <luke@bratch.co.uk> | 2019-09-07 14:02:58 +0100 |
---|---|---|
committer | Luke Bratch <luke@bratch.co.uk> | 2019-09-07 14:02:58 +0100 |
commit | c4e88bfe0c918604cb588ab8b3ce7d29b138cd0f (patch) | |
tree | f061e6a4c1584e515104c9c15f729b823536788b | |
parent | 202061c01eb3600a54f32b4e46327d6685fbd43d (diff) |
Correct some typos with the replay days:hours:minutes syntax help/documentation.
-rw-r--r-- | README | 4 | ||||
-rw-r--r-- | TODO | 2 | ||||
-rw-r--r-- | message.c | 4 |
3 files changed, 6 insertions, 4 deletions
@@ -42,7 +42,7 @@ These options can be changed by issuing a BLABOUNCER REHASH command or by sendin Once connected to blabouncer with an IRC client, you can use the following special blabouncer commands: -"BLABOUNCER REPLAY [[[days:]hours:]minutes:]" (To replay a given length of time of replay log.) +"BLABOUNCER REPLAY [[[days:]hours:]minutes]" (To replay a given length of time of replay log.) "BLABOUNCER QUIT [quit message]" (To quit blabouncer, optionally sending [quit message] to the server.) "BLABOUNCER REHASH" (To reload settings from the configuration file, see above for details.) "BLABOUNCER CLIENTCODE [clientcode]" (To set an identifier for the current client for auto replaying just @@ -53,7 +53,7 @@ Blabouncer commands are all prefixed with BLABOUNCER which you can usually send == Replaying history == You can request that history is replayed at any time by using the command BLABOUNCER REPLAY -[[[[days:]hours:]minutes:]seconds], assuming replaylogging is enabled in blabouncer.conf. +[[[days:]hours:]minutes], assuming replaylogging is enabled in blabouncer.conf. In addition, you can have history automatically replayed upon a client connecting. There are multiple automatic replay methods available by setting "replaymode" in blabouncer.conf: @@ -11,3 +11,5 @@ All the TODOs sprinkled throughout the code! PM replay chat in a channel (or perhaps a random channel?) e.g. replay on 06/09/2019 at 17:05 from 13:49 in #insomnia - maybe a client thing. Ensure replayed lines don't exceed IRC message maximum length due to inserted time/datestamp. + +Log server messages to file. @@ -866,7 +866,7 @@ int processclientmessage(SSL *server_ssl, char *str, struct client *clients, int sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :Valid blabouncer commands are:", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); - snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REPLAY [[[days:]hours:]minutes:]\" (To replay a given length of time of replay log.)", ircdstate->ircnick); + snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REPLAY [[[days:]hours:]minutes]\" (To replay a given length of time of replay log.)", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REHASH\" (To reload settings from the configuration file, see README for which settings can be reloaded.)", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); @@ -1343,7 +1343,7 @@ int processclientmessage(SSL *server_ssl, char *str, struct client *clients, int snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :Unrecognised BLABOUNCER command received. Valid commands are:", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); } - snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REPLAY [[[days:]hours:]minutes:]\" (To replay a given length of time of replay log.)", ircdstate->ircnick); + snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REPLAY [[[days:]hours:]minutes]\" (To replay a given length of time of replay log.)", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); snprintf(outgoingmsg, MAXDATASIZE, "NOTICE %s :\"BLABOUNCER REHASH\" (To reload settings from the configuration file, see README for which settings can be reloaded.)", ircdstate->ircnick); sendtoclient(sourcefd, outgoingmsg, clients, settings, 0); |