Feature #889
Unknown CTCP queries and replies don't work
| Status: | Resolved | Start: | 01/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | seezer | % Done: | 100% |
|
| Category: | Quassel Core | |||
| Target version: | 0.6.0 | |||
| OS: | Any |
Description
Currently, CTCP replies other than PING and VERSION are reported to the server status window as "Received unknown CTCP BLAH by nick!user@host". It also seems, at least from what I gather from #795, that unknown CTCP queries only send the type name of the query, but not any parameters that follow it.
It would be handy if unknown CTCP replies at least displayed as replies, not queries, and also if they would display the data included in the reply. That way, the CTCP TIME and FINGER queries built into the client's nick list context menus would actually be useful.
Associated revisions
Revision d329046faaae47c39af14d9019b542b945e628d7
Handle unknown CTCP stuff a little bit nicer
- unknown replies are now shown with its arguments
Fixes #889
- arguments to unknown CTCP queries are actually transmitted
Fixes #795
- show target's nick for queries
History
Updated by seezer 8 months ago
- Category set to Quassel Core
- Status changed from New to Assigned
- Assigned to set to seezer
- Target version set to 0.6.0
Updated by seezer 7 months ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Applied in changeset d329046faaae47c39af14d9019b542b945e628d7.