I just upgraded to KDE SC 4.10 RC3 and I realized some loss of functionality in kate which is probably related on this commitment: Git commit d51d4820a854985a833f28f1facac9d9287466ab by Christoph Cullmann. Committed on 02/11/2012 at 23:11. Pushed by cullmann into branch 'master'. remove auto bracket feature in kate the auto bracket plugin is much more versatile added to it feature to auto-complete { for tex, too The builtin auto bracket had a very nice feature and when you selected some text, you could embrace it with parenthesis, brackets, quotes or double quotes simply by typing the the corresponding character (,{,",'. Now with the Autobrace plugin, it will remove the highlighted text. Reproducible: Always Steps to Reproduce: 1. Enable Autobrace plugin 2. Write something 3. Select (highlight) this something 4. Press the double quote key Actual Results: something, becomes, "" Expected Results: something, should become, "something"
Confirmed, I've used that feature for years and now it suddenly disappeared after upgrading to 4.10.0. That plugin suggested as replacement doesn't have such features, and even QtCreator recently gained such behavior (as option). Maybe it's good idea to move such things outside core but ONLY if they are complete replacement for all use cases.
I am also a very heavy user of this feature. I've always found the auto-brace plugin lacking and relied on the auto-bracketing option. Besides the missing embracing functionality; the auto-brace plugin still refuses to auto complete { in any of my documents. This is a painful regression that should not have made it upstream.
This is duplicate of https://bugs.kde.org/show_bug.cgi?id=313455 I have a solution and will post it there.
*** This bug has been marked as a duplicate of bug 313455 ***
I'm equally a victim of the above mentioned commit, as the missing features of the original auto bracketing is litereally in my spine, so I constnatly has to correct 'mistypings'. Seems to me like the commit was a hasty decision, and based on faulty assumptions. Until the plugin is on the same level as the built-in fetaure, why not uncommit and put it back in? KSD, MET norway
Also, pressing { used to yield {} (which was good) whereas now it requires a new line before producing the } (which is bad). Also (which was good), with [x] and the cursor after the x, two back spaces would remove all three chars, now (which is bad) the ] is left behind. Also, would like to add my voice to the frustration expressed about losing the ability to highlight and surround with "", '', {}, [] and () At the risk of cross-posting, I`ll put these comments on 313455.