[Top][All Lists]

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

[Weechat-dev] [bug #34180] WeeChat should return an error for /buffer wh

From: Filip H.F.
Subject: [Weechat-dev] [bug #34180] WeeChat should return an error for /buffer when given buffer isn't found
Date: Wed, 31 Aug 2011 12:44:19 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.35 Safari/535.1


                 Summary: WeeChat should return an error for /buffer when
given buffer isn't found
                 Project: WeeChat
            Submitted by: fixato
            Submitted on: Wed 31 Aug 2011 12:44:18 GMT
                Category: commands
                Severity: 3 - Normal
              Item Group: command
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 0.3.5
                IRC nick: FiXato



Since /buffer can except any kind of argument since a buffer can be named just
about anything.
However, if the given buffer name can't be found, it should still return an
error, making it easier to spot typos in commands.

Related log:
<semeion> i was typing /buffer move 48 but for mistake i typed /buffer mode 48
<semeion> and that donĀ“t send me error msg

In this example, if the user doesn't have a buffer named 'mode', it should've
given an error like:
-=- Error: buffer not found or incorrect buffer argument


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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