From: Tod Middlebrook <todmiddlebrook@gmail.com>
To: Bastien <bzg@altern.org>
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/24.3.50.1/elpa/org-20131108/)]
Date: Tue, 12 Nov 2013 04:47:17 -0600 [thread overview]
Message-ID: <87y54t28y2.fsf@gmail.com> (raw)
In-Reply-To: <87mwladulx.fsf@bzg.ath.cx>
Bastien,
I apologize for the mishaps of sending from the wrong address that time
and for somehow leaving off the commentary that I thought was sent with
the code block.
Is it a trivial fix to alter drawer and possibly other element regexps
to never match anything inside of a code block, or should I add it to
http://orgmode.org/tmp/worg/org-issues.html ?
Tod
bzg@altern.org writes:
> Hi Tod,
>
> Tod Middlebrook <whatifitsnot@gmail.com> writes:
>
>> * stuff for bug report
>> #+BEGIN_SRC emacs-lisp
>>
>> (setq org-capture-templates
>> (quote
>> (
>> ("c" "Contacts" entry (file+headline "~/my-stuff/file.org" "Contacts")
>> "* %^{Name: }
>> :PROPERTIES:
>> :EMAIL: %^{Email}
>> :PHONE: %^{Phone number}
>> :NAME: %^{Full Name}
>> :END:
>> %?
>> "))))
>> #+END_SRC
>> :PROPERTIES:
>> :NAME: org-capture-templates
>> :DEPENDS: org
>> :END:
>
> Simply put property drawers right after the headline, or just don't
> put source-code-blocks-containing-property-drawers between headline
> and real property drawers.
next prev parent reply other threads:[~2013-11-12 10:47 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/24.3.50.1/elpa/org-20131108/)] 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 [this message]
2013-11-12 10:59 ` Bastien
2013-11-12 21:28 ` Aaron Ecay
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87y54t28y2.fsf@gmail.com \
--to=todmiddlebrook@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).