emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Bastien <bzg@gnu.org>, Tod Middlebrook <todmiddlebrook@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: property drawers within code blocks interfere [8.2.2 (8.2.2-elpa @ /home/tod/.emacs.d/.cask/]
Date: Tue, 12 Nov 2013 16:28:56 -0500	[thread overview]
Message-ID: <8761rxb97r.fsf@gmail.com> (raw)
In-Reply-To: <87vbzx6g31.fsf@bzg.ath.cx>

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
          :EMAIL: %^{Email}
          :PHONE: %^{Phone number}

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

  reply	other threads:[~2013-11-12 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11  4:11 Bug: property drawers within code blocks interfere [8.2.2 (8.2.2-elpa @ /home/tod/.emacs.d/.cask/] Tod Middlebrook
2013-11-11 16:59 ` Bastien
2013-11-11 22:22   ` Tod Middlebrook
2013-11-12  6:03     ` Bastien
2013-11-12 10:47       ` Tod Middlebrook
2013-11-12 10:59         ` Bastien
2013-11-12 21:28           ` Aaron Ecay [this message]
2013-11-12 21:44             ` Bastien
2013-11-13  8:41               ` Nicolas Goaziou
2013-11-13  8:54                 ` Bastien
2013-11-13  8:34             ` Sebastien Vauban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761rxb97r.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=todmiddlebrook@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).