Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Eric Abrahamsen <e...@ericabrahamsen.net> writes: > >> I was just fooling with this a bit, and am noticing some odd (to me) >> behavior. If I start with emacs -Q, then (goto-char (org-log-beginning)) >> takes me to the start of a :LOGBOOK: drawer, and (org-element-at-point) >> returns the drawer. That works no matter whether the log drawer is >> folded or not. But if the headline is folded, (org-element-at-point) >> returns the headline. >> >> Starting emacs with my usual customizations, it's even weirder than >> that. If I start with the subtree visible but the log drawer folded, >> then this (starting with point in the middle of the headline): >> >> (progn >> (goto-char (org-log-beginning)) >> (org-element-at-point)) >> >> Gives me paragraph. But eval'ing the two lines above consecutively (without >> the progn), gives me the drawer. If the logbook drawer is unfolded, I >> get paragraph every time. >> >> Anyway, I don't know what the expected behavior is, and I don't know how >> outline visibility is supposed to impact document parsing. But this >> seems strange... >> >> All I've customized is: >> >> (setq org-log-into-drawer t) > > This is unrelated to `org-log-beginning'. Point cannot be left in an > invisible area. E.g., the same applies to > > (forward-line 2) (point) > > vs > > (progn (forward-line 2) (point)) > > Anyway, that's a red herring.
Okay, thanks. Since this is part of a function, I guess I should assume the (progn... behavior above, assume `org-element-at-point' is going to return a paragraph, and then work up from there to see if I'm in a log-list. Is that right? Eric
