Bug #1488
Store and display a STATUSMSG correctly
0%
Description
This is just to track and not forget that Quassel's handling of a STATUSMSG needs more work. While mamarley's patch fixed the major issue of treating them as a query, displaying them without the appropriate information (prefix character sent to) is technically incorrect.
As stated in the original issue (#1399), a STATUSMSG is used to communicate with only the users of a specified status (prefix) in a channel. We need to show this prefix to the client, so the end user knows it was a STATUSMSG.
First half: core: these are currently saved as a STATUSMSG type, but the prefix is lost (iirc). We'll need to save this prefix, I'm thinking the best is to add a new column of 'statusmsg'.
Second hand: client: displaying that it's a STATUSMSG. I like the method described in the original issue, i.e "<genius3000:
#mychan>" would be shown as the sender of the message. This may be problematic with view column sizing, and perhaps prepending a "@#mychan" to the message display would be better?
Related issues
History
#1 Updated by genius3000 over 6 years ago
- Related to Bug #1399: Quassel shows STATUSMSG messages as queries added