Modify ↓
Opened at 2005-11-15T13:45:22Z
Closed at 2010-11-21T15:27:40Z
#18 closed defect (wontfix)
Considering namechanges as notice or action
| Reported by: | timing | Owned by: | |
|---|---|---|---|
| Priority: | wishlist | Milestone: | |
| Component: | BitlBee | Version: | 0.99 |
| Keywords: | namechange notice action | Cc: | |
| IRC client+version: | Client-independent | Operating System: | Public server |
| OS version/distro: |
Description (last modified by )
namechanges are like this now:
< root> User joyce’ changed name to there’s no return from 86’
It would be cool if it's a notice:
-!- User joyce’ changed name to there’s no return from 86’
Or an action:
- joyce changed name to `there’s no return from 86’
Viewing the namechange in both the query and #bitlbee is nice too. This'll make bitlbee_nick_change.pl obsolete, but I don't mind.
Attachments (0)
Change History (4)
comment:1 Changed at 2005-11-15T23:23:59Z by
| Description: | modified (diff) |
|---|
comment:2 Changed at 2005-11-15T23:26:40Z by
comment:4 Changed at 2010-11-21T15:27:40Z by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Actually, I tried this in ui-fix and people hated it. So let's forget about it forever.
Note: See
TracTickets for help on using
tickets.
No action, it has to be 101% clear that it's a message from BitlBee, not something from the user. And let's keep it configurable, notices usually end up in the status window if there's no open query window with the sender and some people might not be happy about that.