It appears that as of 0.200, channels declared in the config file are now joined in alphabetical order, rather than the order in which they're declared in the config file, as in past versions. I know many people use clients that may add tabs/windows for channels in lexical order, regardless of the order in which a channel is listed. So those folks won't even notice this change. However, I suspect there are many that also join them in the order in which the server asks the client to join on connect, or the order in which the user joins the channels after connecting. As such, the latter group may have declared their channels in the config to be in an order they prefer. So perhaps a good solution would be to add a config knob at the level, that tells znc which scheme to use when joining predefined channels, such as lexical or none.
It appears that as of 0.200, channels declared in the config file are now joined in alphabetical order, rather than the order in which they're declared in the config file, as in past versions. I know many people use clients that may add tabs/windows for channels in lexical order, regardless of the order in which a channel is listed. So those folks won't even notice this change. However, I suspect there are many that also join them in the order in which the server asks the client to join on connect, or the order in which the user joins the channels after connecting. As such, the latter group may have declared their channels in the config to be in an order they prefer. So perhaps a good solution would be to add a config knob at the <User> level, that tells znc which scheme to use when joining predefined channels, such as lexical or none.
<!-- github-sync-id:2220336 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
It appears that as of 0.200, channels declared in the config file are now joined in alphabetical order, rather than the order in which they're declared in the config file, as in past versions. I know many people use clients that may add tabs/windows for channels in lexical order, regardless of the order in which a channel is listed. So those folks won't even notice this change. However, I suspect there are many that also join them in the order in which the server asks the client to join on connect, or the order in which the user joins the channels after connecting. As such, the latter group may have declared their channels in the config to be in an order they prefer. So perhaps a good solution would be to add a config knob at the level, that tells znc which scheme to use when joining predefined channels, such as lexical or none.
This is related to #104
Closing since we have #104