bugWeeChat - Bugs: bug #27697, python's weechat.command function...


bug #27697: python's weechat.command function doesn't seem checking the "buffer" argument

Submitter:  None
Submitted:  Wed 14 Oct 2009 12:02:52 AM UTC
Category:  script API plugins Severity:  3 - Normal
Item Group:  command Status:  Fixed
Privacy:  Public Assigned to:  flashcode
Originator Name:  Originator Email:  * -email is unavailable-
Open/Closed:  Closed Release:  * 0.3.0
IRC nick:  youshe
* Mandatory Fields

Add a New Comment Rich Markup

Wed 14 Oct 2009 12:02:52 AM UTC, original submission:  

Here's a small code to test the behavior :

def handler_ping(data,buffer,date,tags,displayed,highlight,prefix,message):
        weechat.command(buffer,"/say pong")
        return weechat.WEECHAT_RC_OK


I'm B in buffer 2. C in buffer 3 sends me "ping", I can see an answer pong in buffer 2 from weechat.commant "/say pong" and an answer pong in buffer 3 from weechat.prnt "pong".

This bug may appear in other script languages and in core API, but I haven't tested it.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by flashcode (Updated the item)
  • -email is unavailable- added by None (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-01-23 flashcode Open/ClosedOpen Closed
    2009-10-14 flashcode StatusNone Fixed
        Assigned toNone flashcode

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code