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

Make tab auto-complete go to the shortest matching name first. #4

Davnit opened this issue Apr 19, 2016 · 0 comments


Copy link

commented Apr 19, 2016

I think this is more intuitive than the current behavior of using the channel list order.

If "Bob" and "BobsUncle" are both in the channel, and you press tab after typing "bo", it should go to "Bob" first, then "BobsUncle".

@Davnit Davnit added the suggestion label Apr 19, 2016

nmbook added a commit that referenced this issue May 1, 2016

Auto-complete sort and cboSend event changes
- Should implement #4: Make tab auto-complete go to the shortest matching name first.
- Auto-complete now doesn't use MatchClosest(), this means we lose "@" auto-completion! May come back soon.
  keys now uses the normal listview highlighting ability (instead of .Ghosted)
- Using internal commands with free-form arguments such as /ban, /w, etc are now not processed by the command system:
  this means that lines starting like that will not be split with ";", etc.
  (the list of commands can be customized with Config.ServerCommandList)

@nmbook nmbook closed this May 1, 2016

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