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

Autocomplete wrong case #398

Closed
HelixSpiral opened this issue Apr 13, 2015 · 3 comments
Closed

Autocomplete wrong case #398

HelixSpiral opened this issue Apr 13, 2015 · 3 comments
Assignees
Labels
bug Unexpected problem or unintended behavior
Milestone

Comments

@HelixSpiral
Copy link
Contributor

With weechat.completion.partial_completion_other set to on the case of the nick you're completing can sometimes be wrong (all lowercase)

To reproduce

  • Have two nicks on a channel, I used {Andrew} and {Andrew}|Mobile because they were available on a channel I'm in
  • Set weechat.completion.partial_completion_other on
  • Type {A and tab-complete
  • You will get {andrew} instead of {Andrew}

Now if you add a | to the end of {andrew} and tab-complete you'll get {Andrew}|Mobile with the correct casing.

@Mikaela
Copy link
Contributor

Mikaela commented Apr 13, 2015

I don't have weechat.completion.partial_completion_other as on, but I had similar issue which might or might not be related.

I had query buffer with nickname where the nick is spelled as NickName and tab for some reason decided to autocomplete it wih all small letters.

@flashcode flashcode added the bug Unexpected problem or unintended behavior label Apr 13, 2015
@flashcode
Copy link
Member

This seems to be the same bug as: https://savannah.nongnu.org/bugs/?32213

@flashcode
Copy link
Member

Fixed by #1872, commit f0415c8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants