Closed Bug 953767 Opened 12 years ago Closed 12 years ago

Output error when a command fails

Categories

(Instantbird Graveyard :: Conversation, defect)

Product:
Instantbird Graveyard
Component:
Conversation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: benediktp, Unassigned)

Details

*** Original post on bio 324 at 2010-01-28 21:13:00 UTC *** Right now there is no feedback if a command, for example "/nick" fails for some reason (e.g. nick already taken). Expected behaviour: a sort of system message explaining why the command failed.
*** Original post on bio 324 at 2010-06-07 09:19:02 UTC *** Changing importance to normal since there are cases in which there really is a loss of functionality: for example "no such nick/channel" error messages would be useful to see especially since due to bug 953635 (bio 188) there is no feedback even if sending the message it worked. Having no feedback (looking at the error console is pretty bad feedback;) in both the fail and success case is especially bad in my opinion.
Severity: minor → normal
*** Original post on bio 324 at 2010-06-07 09:20:19 UTC *** Forgive the errors, I should really proofread my posting :S
*** Original post on bio 324 at 2012-04-14 18:13:46 UTC *** Bug 954759 (bio 1327) implemented a nice behaviour in case of failing commands. Setting this one to WFM now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.