Version: 2.5.6 (using KDE 3.5.6, Gentoo) Compiler: Target: i686-pc-linux-gnu OS: Linux (i686) release 2.6.20-gentoo-r5 I never really use code folding. The only time I ever notice it is when I accidentally type some shortcut and my code folds up so I can't see it anymore. It would not be so bad, except that there does not seem to be any way to just "unfold everything" and carry on. There will often be folding markers across the page (dashed lines across, showing the missing code) but no + marker in the margin to unfold with. Also, there will sometimes be + markers in the margin that do not unfold any code. My code is all in python, if that makes any difference.
The shortcut you accidentally typed would have been Ctrl+Shift+- (Collapse Toplevel). The reverse operation you are looking for is Ctrl+Shift++ (Expand Toplevel). Both are also available from the Menu: View->Code Folding. I recommend changing/removing the shortcuts, if this gets in the way too often. You can also hide the border showing the folding markers (F9), so I assume that's the second part of the issue you've been seeing. Kate does have several (reported or yet to be reported) issues with code-folding, but this is not one of them. I'll close this as WORKSFORME. If code-folding still gets in your way, feel free to submit a wish to disable it entirely.
When the problem occurs, I certainly try all of the cold-folding-related menu options (like Expand Toplevel and Expand One Local Level) but nothing will expand the code. There will also be areas where the cursor can disappear in to the folded code. That is, while trying to get the code to unfold, I put the cursor near the fold, then press right- or down-arrow (hoping that when the cursor hits the fold it will pop open) and the cursor will go inside of the fold. When the folding is working properly, that does not happen. The cursor just jumps over the fold.
Ok, I'll reopen. But please, could you try to provide specific instructions on how to reproduce this bug (including wwhich version of KDE you use now, and - if possible - a file where this error occurs)? That will a) allow us to determine whether this is still an issue in KDE 4 b) if it still is an issue (quite possible) it will allow us to actually deal with it effectively.
No more infos, no chance to reproduce or fix that right in KDE 4, sorry...