User <address@hidden> writes: > I don't need this feature at the moment, but the problem > intrigued me, so I came up with a quick implementation. Great! > I don't plan to work on it further, since I don't really need it > yet (I'm a novice org user), but I put it here if someone wants > to develop the idea. > > You simply load the elisp file and from that on folding state is > automatically saved and restored for org mode files. The folding > information is saved at the end of the org file itself every time > the buffer is saved. > > It seemed to work pretty well. The only faulty case I discovered > is when the very last branch is folded in the file, because it > contains the saved folding info, but this bug is probably easy to > fix with a little thinking. Yes, I found this bug. One way to work around this limitation and to safely store the folding information would be to put it in a face property for each headline. Perhaps you have time to dig into that direction? Thanks for this proof-of-concept! -- Bastien
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4