CTCP action sending extra characters
When using certain characters, it seems there are extra characters being sent.
You can only see this when using a client other than quassel.
Not sure of the specifics of whats causing this, or if there are any other characters that are being sent in this way, but it can be easily reproduced by using the \ character in a /me
Example: /me \o/
Will output this in quassel: -*- rikai \o/
But this in other clients: * +rikai \\o/
#1 Updated by rikai over 11 years ago
As requested, adding a note that this was tested against multiple clients. They all interpreted it in the same way that was shown in the example (which was from mirc specifically).the following clients were tested:
- colloquy mobile
- smuxi (i believe so anyway)
#2 Updated by Anonymous over 10 years ago
- Target version set to Some future release
This is made part of the simplified CTCP. MR 148
#3 Updated by Anonymous over 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset quassel|commit:fd92bfb1f093dcc6295ca9de2c34780d288b0fe2.
#4 Updated by Anonymous over 10 years ago
- Assignee set to Anonymous
- Target version changed from Some future release to 0.9.0
Only escape \ with standards-compliant ctcp