Code Completion with One Key Press

User forums > Using Code::Blocks

(1/4) > >>

AlterEgo:
Is it possible to configure Code::Blocks so Code Completion activates after one character key press, rather than three?

I have checked Settings -> Editor -> Code Completion but cannot find an option to adjust the sensitivity there. I apologise if I have overlooked an option to do this. I have also searched for this online but have been unable to find any information on it.

The version of Code::Blocks I'm using is 16.01. Any help you could provide me with this would be much appreciated. Thank you.

BlueHazzard:
settings->Editor->General settings->Code completion->Autolaunch after typing # letters

i don't know why the settings for code completion are split up ???

AlterEgo:
Ah, thank you.

I have another problem now however. I have lost context awareness. As an example, when typing the letter 'p' inside a class, instead of being offered one of the access specifiers, I am confronted with a list of context meaningless keywords.

Is it possible to refine the options given to context sensitive keywords only?

AlterEgo:
To put it another way, have you ever used any of the JetBrains IDE's? In their IDE's, such as IntelliJ IDEA or Android Studio, from typing just one key you get very good, context specific auto complete options. Generally the options given go from most relevant to least. In Code::Blocks at the moment for me, that's not happening. I am given a list of keywords that have no appreciable application within the context they are offered. I end up having to type another few characters to get the options I'm looking for, which defeats the point of starting Code Completion on one key press.

Is it possible to adjust this so that relevant options are given on one key press?

yvesdm3000:
Maybe try the clang code completion ?
The 'staging' branch is the one with most of the features but with some minor regressions that still need to be ironed out, but its workable. Otherwise try the master branch.

Yves

Navigation

[0] Message Index

[#] Next page

Go to full version