emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bastien <bzg@gnu.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
	Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Subject: Re: [bug, beamer] Frame parameters taken from example code block
Date: Tue, 29 Jul 2014 16:06:34 +0200	[thread overview]
Message-ID: <87silkz2c5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87egx4fgn6.fsf@bzg.ath.cx> (Bastien's message of "Tue, 29 Jul 2014 15:17:49 +0200")



Hello,

Bastien <bzg@gnu.org> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>>> Maybe it's time to forbid blank lines between headlines and the
>>> properties drawer?  Or at least to discourage separating them in
>>> the manual?  Otherwise I don't have a steady solution at hand.
>>
>> I think this is fixed already.
>
> Okay, I didn't see any confirmation on the mailing list.

I probably forgot to confirm it. See
ab145f0df553e0bb77795c946ff158d8c069f6e4

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.


Regards,

-- 
Nicolas Goaziou                                                0x80A93738

  reply	other threads:[~2014-07-29 14:06 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 [this message]
2014-07-29 14:10         ` Bastien
     [not found]           ` <87zjfscl33.fsf-E3UqQZAQFPqWIDz0JBNUog@public.gmane.org>
2014-07-29 14:20             ` Sebastien Vauban
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=87silkz2c5.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bzg@gnu.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.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).