[Top][All Lists]

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

[Weechat-dev] [task #13045] Do not run /names upon joining by default

From: Ioannis A
Subject: [Weechat-dev] [task #13045] Do not run /names upon joining by default
Date: Fri, 17 Jan 2014 18:53:31 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0


                 Summary: Do not run /names upon joining by default
                 Project: WeeChat
            Submitted by: superuser
            Submitted on: Fri 17 Jan 2014 18:53:30 GMT
                Category: display
         Should Start On: Fri 17 Jan 2014 00:00:00 GMT
   Should be Finished on: Sun 09 Feb 2014 00:00:00 GMT
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
                IRC nick: 



The default value of _irc.look.display_join_message_ which handles what
happens when you join a channel, is "329,332,333,366". Now, beyond the rather
ugly (presumably RFC-based) values for this variable, 366 is the element
discussed here.

366 basically executes _/names_ every time you join a channel (including when
you open WeeChat).

Now, apart from the fact this spams users' chat logs, it is not actually that
useful. WeeChat by default has a nicklist on the right-hand side of the
screen, rendering /names irrelevant. I presume 366 was made a default before
the nicklist bar was put in place.

Furthermore, the output is not very friendly, especially on large channels; it
is much easier to read nicknames from a nicklist separated by new lines as
opposed to an endless stream of names separated by mere spaces.

Therefore, I propose changing the default value of this to *not display a list
of nicknames* by omitting the _366_ element from the list of values.

I'm submitting this because for me personally, WeeChat's success is due to its
sane defaults. Without them, I would never have tried an ncurses IRC client,
and I am glad WeeChat is around to show me the best way to UX. This is a
simple configuration change that could go a long way towards improving the
little things about WeeChat's UX.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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