emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: Tod Middlebrook <todmiddlebrook@gmail.com>, 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 22:44:08 +0100	[thread overview]
Message-ID: <87vbzxqorb.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8761rxb97r.fsf@gmail.com> (Aaron Ecay's message of "Tue, 12 Nov 2013 16:28:56 -0500")

Hi Aaron and Tod,

Aaron Ecay <aaronecay@gmail.com> writes:

> 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.

Also don't forget the cost in terms of speed.  It's fine to fix the
behavior of Org for such cases, but those cases are rare, and could
be explicitely prevented.  If the general fix does not slow down the
parsing too much, then I'm all for it.  Nicolas might have better
insight here than me.

2 cents,


  reply	other threads:[~2013-11-12 21:44 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
2013-11-12 21:44             ` Bastien [this message]
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=87vbzxqorb.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=aaronecay@gmail.com \
    --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).