emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: #+PROPERTY: for babel header args worked... then it didn't
Date: Thu, 05 Dec 2013 12:02:22 +0100	[thread overview]
Message-ID: <86r49rsgqp.fsf@somewhere.org> (raw)
In-Reply-To: 0c8155a0-e0db-43d0-9a86-5a009707d86a@dewdrop-world.net

James Harkins wrote:
> Wee bit of frustration with Babel just now.
>
> Some weeks ago, I wrote a Beamer presentation with LilyPond source code 
> blocks. I needed to add a little code to each example to suppress the 
> "tagline" from each results file. In that presentation, setting the 
> :prologue header argument in a #+PROPERTY line worked perfectly:
>
> #+PROPERTY: header-args:lilypond :prologue \header{tagline=##f}
>
> Now I'm working on a short article-class document, and I included the same 
> #+PROPERTY at the top, and... no effect. But... *the lines are identical*. 
> ??

I would guess it could be a newly introduced bug, because I did the same
yesterday for R parameters without success...

I ended up with Emacs Local Variables, which does work.

Maybe you could try to bisect Org?

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2013-12-05 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  9:58 #+PROPERTY: for babel header args worked... then it didn't James Harkins
2013-12-05 11:02 ` Sebastien Vauban [this message]
2013-12-05 19:54 ` Achim Gratz
2013-12-06  1:37   ` James Harkins
2013-12-06  8:19     ` 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=86r49rsgqp.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@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).