Hi Tod and Bastien,
The property drawer after the code block is a red herring: the following
file (with no real property drawer at all) misbehaves on property
setting and getting functions, with the fake properties in the code
block behaving as though they pertained to the headline (as can be
confirmed by M-: (org-entry-get nil "EMAIL")):
* stuff for bug report
#+BEGIN_SRC emacs-lisp
(setq i-am-a-string
"
:PROPERTIES:
:EMAIL: %^{Email}
:PHONE: %^{Phone number}
:END:
")
#+END_SRC
I think this problem of unselective regex searches will also affect uses
of e.g. org-scheduled-time-regexp
This seems like an excellent use case for the parser: basically a bunch
of uses of org-*-regexp and org-re-property need to be augmented with
a check like:
(not (memq (org-element-type (org-element-at-point)) '(src-block example-block
...)))
A better alternative might be to use the parser to find the property
drawer in the first place (instead of a regex). Either way, it seems
like the best strategy might be to fix all uses of these problem
variables at once, which is a big undertaking.
--
Aaron Ecay
