Bug 364099 - Code completion does not always suggest exact match first (case sensitive)
Summary: Code completion does not always suggest exact match first (case sensitive)
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: part (other bugs)
Version First Reported In: 16.04.1
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-08 12:45 UTC by Tuukka Verho
Modified: 2019-01-30 08:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tuukka Verho 2016-06-08 12:45:17 UTC 
Version 15.12.3

The code completion does not always suggest the exact match as the primary choice, even though I think it should. Leads to frustration because pressing enter will then mess up what you have just written.

Reproducible: Always

Steps to Reproduce:
For example:
1. Choose QML mode
2. type the word "item", press enter
3. type the word "item" for a second time

Actual Results:  
 The completion will suggest "Item" (capital I) as the first choice. You have to press escape before you can press enter

Expected Results:  
The exact match "item" should be suggested first
Comment 1 Buovjaga 2016-07-08 19:21:33 UTC 
Reproduced.

Arch Linux 64-bit
Kate 16.04.2
KDE Frameworks 5.23.0
Qt 5.7
xcb wm
Comment 2 Ahmad Samir 2019-01-30 08:57:28 UTC 
I couldn't reproduce the issue with version 18.12.0. Feel free to reopen if you still experience this issue.