[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Weechat-dev] [bug #37375] go.py fails to move to the appropriate buffer
From: |
anonymous |
Subject: |
[Weechat-dev] [bug #37375] go.py fails to move to the appropriate buffer |
Date: |
Mon, 17 Sep 2012 15:21:00 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 |
URL:
<http://savannah.nongnu.org/bugs/?37375>
Summary: go.py fails to move to the appropriate buffer
Project: WeeChat
Submitted by: None
Submitted on: Mon 17 Sep 2012 03:20:59 PM UTC
Category: scripts
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name:
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 0.3.9-dev
IRC nick: ldvx
_______________________________________________________
Details:
When you you use the buffer merge feature and you use go.py to move you to the
buffer containing certain channel/nick, go.py takes you to the buffer number,
rather than the specific buffer.
I.e. I have the buffer list
[1] (core) weechat (notify: highlight)
[1] (irc) server.fn (notify: highlight)
[1] (irc) server.im (notify: highlight)
[1] (irc) im.&bitlbee (notify: highlight)
[1] (irc) server.jb (notify: highlight)
[2] (irc) fn.#archlinux (notify: highlight)
I want to go to buffer weechat, but the current 'focus' is in buffer
server.fn, /go weechat will work as /buffer 1, rather than /buffer weechat.
This becomes immediately apparent if you're using the zooming feature for
merged buffers.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?37375>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [Weechat-dev] [bug #37375] go.py fails to move to the appropriate buffer,
anonymous <=