Bug 308614

I switched (back) to KDevelop from Qt Creator, and while I find that KDevelop's editor is much nicer, and the auto completion in general much smarter, there is one issue that is really annoying:

The "auto bracket" feature does not take context into account at all. This means

1) The closing bracket is always added regardless if there is a matching number of opening brackets. This often leads to superfluous closing parens, especially visible when auto-completing connect() calls. This is also annoying when editing existing code where the closing bracket is already in place. Another occurance is quotes - often when editing strings, I will remove the opening quote while the end of the string with the closing quote is still in place, and KDevelop unhappily adds another pair of quotes.

2) When deleting code inside a pair of brackets, the closing bracket is removed too even though the matching opening one is still there.

3) Often when typing fast, I type a closing bracket automatically. While not technically a bug, it would be a nice feature to "ignore" that extra bracket in these cases. Qt Creator does it this way (if you type the closing bracket right after it had already been auto-completed, it won't add another one) and it really helps.

4) There should be no autocompletion of apostrophes inside comment blocks. After all, the apostrophe in English text usually shows up as a single :)


Reproducible: Always

Steps to Reproduce:
Enable general auto completion and "Auto Brackets" and start coding. Try things like connect() calls (with auto-completion of SIGNAL and SLOT) and see how you get superfluous closing characters...
Actual Results:  
See above.

Expected Results:  
I think the overall experience could be improved drastically with the following improvements:

1) Always try to match the number of open parens/brackets/quotes/whatever when autocompleting. Don't add more than necessary.
2) Ignore a typed paren/bracket/quote/whatever if the same character has just been autocompleted and there's no matching open character
3) Don't autocomplete apostrophes in comment blocks
4) Just look at how Qt Creator handles it, it proved to be an almost perfect experience for me