Rasmus writes:
> Out of curiosity, why is it "more" consistent to return paragraph
> here?
Notwithstanding this case, if `org-element-at-point' returns
`special-block', you /know/ that you are either on block boundaries
(#+begin_special or #+end_special) or on any affiliated keyword above,
but /
Hi Nicolas,
Thanks for the helpful reply.
Nicolas Goaziou writes:
>> Is there a reason why org-element-at-point reports the type to be a
>> paragraph for special blocks? E.g. in the examples at the bottom of this
>> mail, where | is the cursor, the types are: export-block, src-block and
>> par
Hello,
Rasmus writes:
> Is there a reason why org-element-at-point reports the type to be a
> paragraph for special blocks? E.g. in the examples at the bottom of this
> mail, where | is the cursor, the types are: export-block, src-block and
> paragraph with a nested special block.
This is a co
Hi,
Is there a reason why org-element-at-point reports the type to be a
paragraph for special blocks? E.g. in the examples at the bottom of this
mail, where | is the cursor, the types are: export-block, src-block and
paragraph with a nested special block.
Is there a neat way to detect if point i
