Opened 14 years ago

Closed 13 years ago

#2440 closed defect (fixed)

CTCPs not handled properly by IRC activity

Reported by: fran Owned by: fran
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Irc Version: Git as of bugdate
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

The Sugar IRC activity doesn't recognize CTCP messages; it instead displays the raw text as a private message surrounded by \001 characters.

For example, Freenode's bot "frigg" usually CTCP VERSIONs users when they connect; so upon starting the IRC activity in its default configuration, one will get the private message "\001VERSION\001" from frigg.

Attachments (1)

0001-Add-proper-CTCP-support-sending-and-receiving.patch​ (6.3 KB) - added by fran 13 years ago.
Add proper CTCP support - sending and receiving

Download all attachments as: .zip

Change History (4)

comment:1 Changed 13 years ago by fran

  • Owner changed from mchua to fran
  • Status changed from new to accepted

Changed 13 years ago by fran

Add proper CTCP support - sending and receiving

comment:2 Changed 13 years ago by fran

I've fixed this by adding proper support for sending and receiving CTCPs in the IRC activity. I've attached the patch above.

comment:3 Changed 13 years ago by fran

  • Resolution set to fixed
  • Status changed from accepted to closed

Patch applied to mainline.

Note: See TracTickets for help on using tickets.