Bug 345028 - Entering a single character can trigger auto complete popup
Summary: Entering a single character can trigger auto complete popup
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.7.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-10 21:48 UTC by Thomas Fjellstrom
Modified: 2016-09-08 20:23 UTC (History)
0 users

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


Attachments
screenshot (426.26 KB, image/png)
2015-03-10 21:48 UTC, Thomas Fjellstrom
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Fjellstrom 2015-03-10 21:48:05 UTC
Under some circumstances entering a character can trigger the auto complete popup.

Please see: http://i.imgur.com/RuEEUwF.png

It does not seem to happen in another file I tried it in. This happens with numbers and letters.

Reproducible: Always

Steps to Reproduce:
1. type a single character
2. watch popup appear

Actual Results:  
auto complete popup shows when entering a single character.

Expected Results:  
auto complete should only popup after a (possibly configurable) number of characters are entered.
Comment 1 Thomas Fjellstrom 2015-03-10 21:48:45 UTC
Created attachment 91524 [details]
screenshot
Comment 2 Kevin Funk 2016-09-08 20:23:31 UTC
Hello!

We are working on a new clang-based C/C++ language plugin for KDevelop 5 which
supersedes the old C++ plugin in KDevelop 4. See e.g.:
https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available

Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather
want to supply a good Clang based C++ experience for KDevelop 5 than wasting
our time on the legacy C++ support for KDevelop 4.

With the new clang-based C/C++ language plugin, the bug presented here does not
occur. In my testing. For these reasons, I'll close this bug. Please stay tuned
for KDevelop 5.

If you think this bug is applicable to Clang/KDevelop 5, please reopen the
report and add new information on how to reproduce the bug there.

Note: If you reopen this, please post a minimal working example which we can use to reproduce the issue.