Bug 187320 - user can't change away status to not-away
Summary: user can't change away status to not-away
Status: RESOLVED NOT A BUG
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-16 18:01 UTC by andreas.davour
Modified: 2009-03-16 18:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andreas.davour 2009-03-16 18:01:03 UTC
Version:           1.0.1 (using 3.5.10, Kubuntu (hardy) 4:3.5.10-0ubuntu1~hardy1.1)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.24-22-generic

I was logged in to a server, and had joined a channel. After the work day was over I turn me status to away (/away home) and went home.

When I cam back to work I tried to go back from my away state (/away <cr>) and nothing changed. The indicator next to the textbox where I type stuff to appear in the channel still lists me as "(away)" and that's also the case in the nick list pane to the right.

I expected it to go away and me to be "online" or whatever the state is when you're not "away".
Comment 1 Eike Hein 2009-03-16 18:05:42 UTC
In Konversation 1.0.x, "/away" always sets the away state (if entered without an argument, a default away message is used). You can use "/unaway" or "/back" to return.

In Konversation 1.1 (the current stable release, which you should upgrade to - it's worth it; the auto-away/return support might remove your need to do this manually for example), "/away" is a toggle: "/away" always sets away when unaway, with or without an argument, but "/away" without an argument sets unaway when away at the time.