Hi, I don't remember if this was reported or not. I frequently get the following message in the mini-buffer, after trying to expand the last top-level node in a file. The behavior seems to depend on the last node containing a plain list.
byte-code: Invalid search bound (wrong side of point) This issue occurs if org-cycle-include-plain-lists is set to 'integrate'. If I change it back to the default 't', then I get a different incorrect behavior. Example (with org-cycle-include-plain-lists = integrate): ~~ Contents * I ** A * II ** B - Plain list ~~ Hit shift-tab to collapse everything: ~~ Visible contents * I... * II... ~~ Now put the insertion point anywhere on "* II" and hit tab to expand the sub tree. Here's where I get that message. The normal behavior of TAB visibility cycling is: TAB once: Expand to show the node's immediate children, but the children are collapsed. TAB again: Expand everything underneath the current node. TAB again: Collapse, to show only the current node. When I get the message, I only get #1 and #3 behaviors. I can't hit TAB twice on the heading to see everything underneath. Now, if org-cycle-include-plain-lists = t, hitting TAB twice does expand the plain list, but unfortunately it will not display the last character: ~~ Result of TABx2 with the point on "* II" * I... * II ** B - Plain lis... ~~ I haven't found a keystroke that will make "t" of "list" reappear. "t" is actually still there (copy and paste will demonstrate that), but the visibility code seems to think that something at the end is supposed to be hidden, even if just one character. Org-mode version 8.0-pre (release_8.0-pre-215-g8ccbc7 @ /home/dlm/share/org-mode.git/lisp/) Thanks, hjh
