Changeset 2d2e6d1fb24e5d687eab7e77bf251ad777ca736d

Show
Ignore:
Timestamp:
08/09/08 22:25:41 (3 months ago)
Author:
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
git-committer:
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> 1218306341 +0200
git-parent:

[bf8d3dc80f6103fdd8e2a629880ab0470d516d70]

git-author:
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> 1218306341 +0200
Message:

message.rb: correct @plainmessage and @message for CTCP messages

After CTCP parsing, @plainmessage was not defined correctly (as it still
contained the CTCP command), and @plainmessage and @message were not
being cleaned up correctly.

This manifested itself e.g. with spurious \001ACTION and other strange
unusual byte sequence popping up in markov-generated text.

Fix by redefining @plainmessage and @message appropriately in CTCP
handling.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • lib/rbot/message.rb

    r9769ffe r2d2e6d1  
    358358        debug "Received CTCP command #{@ctcp} with options #{@message} (action? #{@action})" 
    359359        @logmessage = @message.dup 
     360        @plainmessage = BasicUserMessage.strip_formatting(@message) 
     361        @message = BasicUserMessage.strip_initial_formatting(@message) 
    360362      end 
    361363