Hi List, I managed to copy and adapt the Org speed-commands to outshine.el, so that one can enjoy the one-key navigation and cycling commands in (outshine) source-code buffers too. This works well, although there is obviously a lot of cycling going on when exploring a source file with these speed commands.
Another feature I tried to copy from Org-mode is the hiding of :ARCHIVED: subtrees - I would find it very handy to have dedicated (and maybe extensive) :comment: tagged headers in (outshine) source-code files that stay folded and don't get in the way when navigating or cycling the buffer. I copied and adapted stuff from Org-mode that seems to work somehow - but when I add the hook to `outline-view-change-hook' I immediately get the `max-lisp-eval-depth' exceeded error (its set to 600 in my system). Org-mode functionality is always more complex than what is needed for outshine, I cannot simply copy&paste or require existing stuff. But I wonder what is the magic behind the Org-mode hooks like `org-cycle-hook' - how do they avoid exceeding 'max-lisp-eval-depth' when there are constant visibility state changes in reasonable big Org-files? Or should it work even for bigger files and there must be an error on my side (e.g. in loops/recursions)? I'm not sure how powerful Emacs is w.r.t. this, i.e. how easy it is to bring it to the its limits with such a hook that is triggered all the time. -- cheers, Thorsten
