weechat-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Weechat-dev] [bug #29022] /away -all doesn't set future away


From: anonymous
Subject: [Weechat-dev] [bug #29022] /away -all doesn't set future away
Date: Sat, 27 Feb 2010 16:48:18 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10

URL:
  <http://savannah.nongnu.org/bugs/?29022>

                 Summary: /away -all doesn't set future away
                 Project: WeeChat
            Submitted by: None
            Submitted on: Sat 27 Feb 2010 04:48:17 PM UTC
                Category: commands
                Severity: 3 - Normal
              Item Group: command
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 0.3.1
                IRC nick: Specimen

    _______________________________________________________

Details:

The command /away sets the away status for the server where the command is
issued, if the server is not connected it sets "future away".
When using /away -all and a server which has buffers opened is not connected
(normally because the connection dropped and it's reconnecting) it doesn't set
"future away".

This might not be exactly considered a bug but a feature request, depending
if this behaviour is intended or not.

If /away -all had a similar behaviour to /away it would be helpful for how
auto-away scripts behave and it would have a more consistent behaviour.




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?29022>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]