Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto complete the active (channel) buffer first (and optionally group by network) #392

koobs opened this Issue Apr 11, 2015 · 3 comments


None yet
3 participants
Copy link

koobs commented Apr 11, 2015

Currently, it appears that weechat (as of 1.1.1) auto-completes channel names as a single alphabetically sorted list, even when on multiple networks.

This is an enhancement request to:

  • Auto-complete the active (channel) buffer first when completing #<matchtext>.
  • An option could / should be created such as weechat.completion.channel_active_first=on|off.
  • An option to group channel completion list by network, such that if on network1 and network2, completion will cycle through all network1 channel buffers first, then cycle through network2 channel buffers. Suggested option name weechat.completion.channel_group_by_network=on|off.

Note: Existing Savannah task #12923: Channel completion

flashcode added a commit that referenced this issue Nov 16, 2015

@flashcode flashcode self-assigned this Nov 16, 2015

@flashcode flashcode closed this in c337e74 Nov 17, 2015


This comment has been minimized.

Copy link

koobs commented Nov 18, 2015

Thank you! Just to confirm, the suggestions options to globally enable/disable this, and/or group networks has not been added correct?


This comment has been minimized.

Copy link

flashcode commented Nov 18, 2015

Yes, I think options are not even needed, so this is the new default behavior.
You can still complete as usual with #something [+TAB], all matching completions will be used (even if not sorted alphabetically).

@flashcode flashcode added this to the 1.4 milestone Nov 18, 2015


This comment has been minimized.

Copy link

bendem commented Nov 26, 2015

Would be neat if that worked with prefixed channels as well like /msg @#<channel> <msg>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.