Modify ↓
Opened at 2011-11-21T11:49:14Z
Closed at 2012-12-07T00:05:57Z
#864 closed enhancement (fixed)
Report error messages in appropriate channel
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Version: | 3.0.3 | |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: | Xubuntu 11.04 AMD64 |
Description
When an error is generated (e.g. message too long for Twitter), the error message is sent to &bitlbee. It'd make a lot more sense to send it to the channel where the erroneous event occurred (e.g. #twitter_whomever). This way you don't have to switch back to the &bitlbee tab just to see what went wrong with sending your message.
Attachments (0)
Change History (2)
comment:1 Changed at 2012-12-06T23:53:22Z by
Component: | BitlBee → Twitter |
---|
comment:2 Changed at 2012-12-07T00:05:57Z by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Closing this one in favour of #996. This bug has been fixed in the JSON branch, which will be merged and release fairly soon.