Bug 335591 - There is no way to reverse the effect of "Fold Toplevel Nodes"
Summary: There is no way to reverse the effect of "Fold Toplevel Nodes"
Status: RESOLVED NOT A BUG
Alias: None
Product: kate
Classification: Applications
Component: folding (show other bugs)
Version: 3.13.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-30 13:30 UTC by Cristian Tibirna
Modified: 2014-05-30 17:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Tibirna 2014-05-30 13:30:11 UTC
In Kate->View->Code Folding, there is "Fold Toplevel Nodes", the only folding command with a default shortcut. This shortcut is chosen to be Ctrl+Shift+-, which is very easy to hit by mistake, while e.g. tuning the font size with Ctrl+- and Ctrl++ shortcuts.

Unfortunately, there is no way to undo/reverse the effect of folding all toplevel nodes, apart from going and unfolding manually each and every toplevel node. In a typical Python code file, for example, this could mean tens of tedious mouse positionings and clicks.

The documentation (for which btw. kate 3.13 is still that of that of kate 3.11) states "Click on the right pointing triangle to expand all toplevel regions" which is at least confusiong (*which* right pointing triangle?) if not sarcastic.

Fortunately, quitting kate, restarting it and reopening the same document brings back the unfolded file, "thanks" to bug 316184.

Reproducible: Always

Steps to Reproduce:
1. Open a document with many toplevel nodes (e.g. a Python module file)
2. Hit "Ctrl+Shift+-" (default shortcut) or click View->Code Folding->Fold Toplevel Nodes
3. Try to unfold everything.
Actual Results:  
There is no way to unfold all toplevel nodes with one single command. One has to go and unfold each node, one at a time.

Expected Results:  
There should exist a "Unfold Toplevel Nodes" action.
Comment 1 Christoph Feck 2014-05-30 17:48:18 UTC
Reported as bug 335590.