[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Weechat-dev] [task #13052] improve the behavior of /buffer
From: |
anonymous |
Subject: |
[Weechat-dev] [task #13052] improve the behavior of /buffer |
Date: |
Tue, 21 Jan 2014 08:21:17 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 |
URL:
<http://savannah.nongnu.org/task/?13052>
Summary: improve the behavior of /buffer
Project: WeeChat
Submitted by: None
Submitted on: Tue 21 Jan 2014 08:21:16 AM UTC
Category: commands
Should Start On: Tue 21 Jan 2014 12:00:00 AM UTC
Should be Finished on: Tue 21 Jan 2014 12:00:00 AM UTC
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Originator Name: sam113101
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
IRC nick:
_______________________________________________________
Details:
When giving a partial name to /buffer, e.g. "/buffer partialname", weechat
will switch to the first buffer having a name which contains "partialname".
The full name could be irc.freenode.#partialname
When, for example, both "#partialname" and "partialname" buffers exist,
"/buffer partialname" might not land you on "partialname" as you would expect,
even though "partialname" matches more closely "partialname" than
"#partialname" does.
I think it could be improved.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?13052>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Weechat-dev] [task #13052] improve the behavior of /buffer,
anonymous <=