Open
Bug 319199
Opened 19 years ago
Updated 8 years ago
valid /command should never produce no apparent result
Categories
(Other Applications :: ChatZilla, enhancement)
Other Applications
ChatZilla
Tracking
(Not tracked)
NEW
People
(Reporter: mrmazda, Assigned: rginda)
References
(Depends on 1 open bug)
Details
Tested on Linux trunk and OS/2 trunk, 0.9.67+ and 0.9.69 To reproduce: 1-open Chatzilla with usermode +R 2-open any channel with unregistered nick(s) 3-do '/ctcp somenick version' on somenick who is unregistered Actual result: 1-(nothing) in output window 2-(nothing) in JS Console Expected result: 1-something in the output window, either a good ctcp return, since it was an invited response, or a message either that the command requested cannot be completed, or the output is blocked by usermode +R
Comment 1•19 years ago
|
||
It's impossible to know if the response was blocked. We can't even know what +R means for any particular network. So the only other option is for every ctcp command to output a line in the view saying it was run. Is that really what you want? "You have sent a "VERSION" request to <nick>". recommending WONTFIX...
Severity: normal → enhancement
Hardware: Other → All
Reporter | ||
Comment 2•19 years ago
|
||
I really don't care what happens as long as it is not apparently nothing, so that I know that whatever I did actually happened, and didn't disappear into the ether or cause an error message I somehow missed. "You have sent a "VERSION" request to <nick>" would be perfectly fine with me. A tooltip over the input window would probably be fine too, though this particular tooltip would need to persist for some time long enough to be noticed, or a statusbar message saying what happened, also with extra persistence. Probably I'd prefer something in the output window, because that's where everything else I type in the input window somehow creates some additional output. Don't confuse the particular repro with the summary. This bug is about always seeing *something* happen as a result of something entered in the input window. At least at a shell prompt when you run something that outputs nothing to the screen you get a shell prompt back. I'd like some sort of analogy to apply in CZ.
Comment 3•18 years ago
|
||
(In reply to comment #2) > I really don't care what happens as long as it is not apparently nothing, so > that I know that whatever I did actually happened, and didn't disappear into > the ether or cause an error message I somehow missed. Error messages would be in the JS console (which you can check) or displayed in the output window (or both). Whether or not something got lost in the ether is something we can't determine. > "You have sent a "VERSION" request to <nick>" would be perfectly fine with me. To me, that sounds really, really lame. I don't want everything I do to spam my output window. The reply/ies are wordy enough as it is, in some cases. > A tooltip over the input window would probably be fine too, though this > particular tooltip would need to persist for some time long enough to be > noticed, or a statusbar message saying what happened, also with extra > persistence. Probably I'd prefer something in the output window, because that's > where everything else I type in the input window somehow creates some > additional output. ... and where I want to read something useful, not a history of everything I did to CZ. > Don't confuse the particular repro with the summary. This bug is about always > seeing *something* happen as a result of something entered in the input window. The only thing I can think of that I could possibly live with is changing the status bar for a set amount of time (say, 3 seconds), after which it should resume normal functionality. Otherwise, I suggest WONTFIX. > At least at a shell prompt when you run something that outputs nothing to the > screen you get a shell prompt back. I'd like some sort of analogy to apply in > CZ. A shell prompt has a concept of 'returning' from a command you gave it. In async communication like IRC that's simply nonexistant (unless we'd implement our own 'timeout' system, which would just make things worse), making your request impossible.
Reporter | ||
Comment 4•18 years ago
|
||
(In reply to comment #3) > (In reply to comment #2) > > "You have sent a "VERSION" request to <nick>" would be perfectly fine with me. > To me, that sounds really, really lame. I don't want everything I do to spam my > output window. The reply/ies are wordy enough as it is, in some cases. You're an advanced user. I doubt most normal or novice users would think it's spam. Normal users more likely want to know something actually happened as a result of something they did.
Updated•15 years ago
|
QA Contact: samuel → chatzilla
You need to log in
before you can comment on or make changes to this bug.
Description
•