| Summary: | user can't change away status to not-away | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | andreas.davour |
| Component: | general | Assignee: | Konversation Bugs <konversation-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | hein |
| Priority: | NOR | ||
| Version First Reported In: | 1.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
andreas.davour
2009-03-16 18:01:03 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. |