[Konversation-devel] [Bug 136743] /away w/o arguments does not un-set away-status

[Eike Hein]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=136743         




------- Additional Comments From hein kde org  2006-11-03 01:46 -------
> IMHO, whereever possible, commands that correspond one-to-one to protocol commands should work as closely to how they work in the protocol as practical.

I disagree, because I don't see the protocol as particularly relevant to the interface presented to the user, nor as a guide on how to implement it. And with AWAY specifically, going by the language in RFC 1459, I don't think it was intended to be, either. This is clearly for machines, not humans.

Once you've managed to think outside of the restrictions imposed by trying to model the interface after the low-level protocol, it's pretty apparent that unsetting away by issueing /away is rather moronic and unintuitive (not so for machines, but for humans). And that's what I care about. I'm willing to make concessions to old-timers as the compromise suggested above when I'm reasonably convinced that they won't compromise that premise, but not when they do.


> Realistically, a new IRC user is going to point and click anyway. 

New users don't stay new users for very long: They quickly realize that typing commands is faster than clicking, and gradually adopt the usage of text commands. When they do, it's nice that the commands make sense intuitively, and don't require for them to learn about implementation details of the IRC protocol that modern IRC clients mask. (Taking a quick look at X-Chat, it happens to implement the toggle compromise. Konvi and X-Chat combined make up most of the GUI client market share on the Linux/Unix platform, I'd venture to say.)