Sorting an IRC channel after all other buffers results in odd behaviour. about weechat-autosort HOT 2 CLOSED

Note that for me, these settings worked as expected:

autosort: Sorting rules:
    0: core = 0
    1: irc = 2
    2: i3 = 99
    3: * = 1
    4: irc.server = 1
    5: irc.irc_raw = 0
    6: irc.server.*.#* = 0
    7: irc.server.*.[*]status = 1
    8: irc.server.*.[*]* = 2
autosort: Replacement patterns:
    0: ## -> #
    1: irc.freenode.#i3 -> i3

Maybe there are some subtle Python version dependent behaviour. My weechat is using python 2.7.13. @squigglezworth: Could you check your python version?

from weechat-autosort.

After some more debugging on irc, I think the observed behaviour can be explained.

The first replacement pattern used was freenode.#i3 -> i3. That caused the buffer name after replacement patterns were applied to be irc.i3. The group_irc option then turned that into irc.server.i3 before the sort rules were applied. In sort rules * doesn't match periods, so the sort rule *i3* never matched the correct buffer and it ended up being sorted alphabetically with the server buffers.

During debugging we did try a number of replacement patterns and sort rules, but apparently never the correct combination at the same time. With the replacement pattern freenode.#i3 -> i3 and group_irc = on, the correct sort rule would be irc.server.i3 = .... With group_irc= off it would be irc.i3 = ....

Alternatively, the replacement pattern irc.freenode.#i3 -> i3 can be used with the rule i3 = .... This doesn't behave exactly the same as the previous option, so both can be valid use cases.

It also got me thinking that a /autosort debug command to show the result of replacement patterns and sort rules might be useful, but thats a seperate issue. The same goes for allowing regexes or glob-style patterns in sort rules.

from weechat-autosort.