From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Bastien <bzg-mXXj517/zsQ@public.gmane.org>,
Nicolas Goaziou
<mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: [bug, beamer] Frame parameters taken from example code block
Date: Tue, 29 Jul 2014 16:20:31 +0200 [thread overview]
Message-ID: <86mwbs2qmo.fsf@somewhere.org> (raw)
In-Reply-To: <87zjfscl33.fsf-E3UqQZAQFPqWIDz0JBNUog@public.gmane.org> (Bastien's message of "Tue, 29 Jul 2014 16:10:08 +0200")
Bastien wrote:
> Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> writes:
>
>> As a side note, "forbidding" blank lines between headlines and the
>> properties drawer (or better just after the planning line, if any) would
>> make parsing easier and faster in a lot of cases. Unfortunately, I think
>> this would break a lot of files, too.
>
> Well, we can poll users and see how inconvenient this change would be.
>
> (I'm certainly biased here, as I never use blank lines between the
> headline and the properties drawer.)
>
> If it's not too inconvenient, we can plan this for Org 9.0.
Sorry for taking too much time to answer, but I'm under constant flood
here, because of holiday times and the such.
First, please note I wouldn't flag the bug as being caused by a property
drawer detached from the headline. For me, the problem (in the ECM
I gave) is interpreting the contents of the Org code block (in the given
case: an headline with a property drawer following it).
I regard that "interpretation" of what's inside the Org code block as
the real cause of the problem. Maybe interpretation is not the right
term, but the code block should never be allowed to be scanned when
searching properties of the current headline IMHO.
Second, I neither never ever have property drawers separated from
headlines. I think that could be safely enforce, anyway, as all the
tools in Org (C-c C-x p, C-c C-x C-i, C-c C-s, C-c C-d, etc.) never make
such a case appear.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-07-29 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 12:01 [bug, beamer] Frame parameters taken from example code block Sebastien Vauban
2014-06-18 12:12 ` Sebastien Vauban
2014-07-28 14:24 ` Bastien
2014-07-28 19:25 ` Nicolas Goaziou
2014-07-29 13:17 ` Bastien
2014-07-29 14:06 ` Nicolas Goaziou
2014-07-29 14:10 ` Bastien
[not found] ` <87zjfscl33.fsf-E3UqQZAQFPqWIDz0JBNUog@public.gmane.org>
2014-07-29 14:20 ` Sebastien Vauban [this message]
2014-07-31 11:47 ` Nicolas Goaziou
2014-08-01 11:54 ` Bastien
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=86mwbs2qmo.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=bzg-mXXj517/zsQ@public.gmane.org \
--cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.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).