- Apr 13, 2019
-
-
Dominik Honnef authored
-
- Nov 26, 2018
- Nov 19, 2017
-
-
Renne Nissinen authored
-
Renne Nissinen authored
-
Renne Nissinen authored
-
Renne Nissinen authored
-
Renne Nissinen authored
-
Renne Nissinen authored
-
- Jun 19, 2017
-
-
bougyman authored
Adds .ruby-{version,gemset} to .gitignore
-
- Jun 18, 2017
- May 31, 2017
-
-
Defman21 authored
Signed-off-by: Defman21 <i@defman.me>
-
- May 30, 2017
- May 29, 2017
-
-
Ken Spencer authored
-
- Nov 19, 2016
-
-
Alexandre ZANNI authored
So user didn't konw the irc serve while reading teh readme.
-
- Jun 03, 2016
- May 23, 2016
-
-
rjhornsby authored
Closes: gh-227 [via git-merge-pr]
-
- Apr 26, 2016
-
-
Dominik Honnef authored
-
- Apr 25, 2016
-
-
Dominik Honnef authored
-
Dominik Honnef authored
-
- Dec 17, 2015
-
-
Dominik Honnef authored
-
- Dec 11, 2015
-
-
Steve Soltys authored
-
- Nov 01, 2015
-
-
Dominik Honnef authored
-
- Oct 27, 2015
-
-
Peter Tseng authored
Under certain code paths, using select! instead of select would lead to modifying the plugin's hooks, instead of just a local copy. This effectively broke hooks when using more than one event type. Fixes gh-207
-
- Oct 26, 2015
-
-
Dominik Honnef authored
d0ede97d broke the way we were doing logging. Previously, a call to LoggerList#method would correspond to calls to Logger#method – after the change, they resulted in Logger#log calls only. This was made under the assumption that loggers only overwrote the format_* methods – However, they're also free to overwrite the incoming, outgoing, exception, ... methods. This change restores the old behaviour by calling these methods again.
-
Dominik Honnef authored
-
- Oct 25, 2015
-
-
Dominik Honnef authored
Log filters take log messages as input and return modified messages. Additionally, they can drop messages by returning nil. This allows for filtering passwords or other information from log messages. Closes gh-194
-
Dominik Honnef authored
Document that using Channel.new and User.new aren't the correct way of obtaining instances of these classes, and that one should use ChannelList and UserList instead. Thanks to Simon Lundström for an attempted patch. Closes gh-203
-
Dominik Honnef authored
-
Dominik Honnef authored
Some IRC servers support STATUSMSG. STATUSMSG allows sending messages to a subset of a channel's users, based on their mode. By sending a message to +#channel, only people who have voice or higher will receive the message. Previously, Cinch didn't take this into account at all. Message#channel would be nil and Message#reply only worked by chance (Cinch thought that +#channel was a user and replied to it). The new support explicitly supports STATUSMSG. For a message sent to +#channel, Message#channel will return #channel and Message#reply will reply to +#channel. Additionally, an attribute called Message#statusmsg_mode was added, which would contain the STATUSMSG mode that was addressed, using mode characters, not sigils. For +#channel, statusmsg_mode would be "v". There is currently no direct support for sending arbitrary STATUSMSG messages. That is, Channel has no APIs for it. Users who really need it have to construct their own Target instance. New APIs might be added in the future.
-
Dominik Honnef authored
-
- Oct 23, 2015
-
-
Dominik Honnef authored
-