User <address@hidden> writes: > User <spamfilteraccount <at> gmail.com> writes: >> >> The folding information should simply be saved into a separate >> file. For example, for notes.org the accompanying folding >> information could be in notes.org.fold. The posted code can be >> trivially modified to behave this way and with this change the >> actual content of the org file is not affected at all and we have >> a pretty usable folding save/restore extension for org. > > > The thing pestered me, so I fixed it to take care of it. > > Now folding information is saved into a separate file and it is > saved when the buffer is closed (but only if the buffer is saved > to disk to avoid saving folding info for discarded buffers). > > I fixed the algorithm too, because it was buggy. Now it's working > well and it's also simpler. Hey, that's nice. I was just about to suggest: "Why not using a VISIBILITY property for that?" (that would spare us the additional file..) but you were faster than me! :) Thanks for this, -- 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