#+PROPERTY: for babel header args worked... then it didn't

#+PROPERTY: for babel header args worked... then it didn't

[James Harkins]

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

":prologue \header{tagline=##f}" does take effect if I include it in every 
#+begin_src line. That's an acceptable workaround for this file, since 
there won't be many examples.

But it bothers me when I figure something out, and then I try to do it 
again, and it doesn't work. It's like 1 + 1 = 2 in one place, and 1 + 1 = 0 
in another.

Why would "#+PROPERTY" work in one file and be ignored in the other?

hjh


Header of the working file:
~~
#+BIND: org-latex-listings-options (("basicstyle" "\\ttfamily\\scriptsize") 
("captionpos" "b") ("tabsize" "3"))

#+PROPERTY: header-args:lilypond :prologue \header{tagline=##f}

#+LANGUAGE:  en
#+OPTIONS:   H:2 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t ':t
# #+OPTIONS:   c:nil creator:comment d:(not LOGBOOK) date:t e:t email:nil
#+OPTIONS:   email:nil
#+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport

#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_THEME: default
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col) 
%8BEAMER_opt(Opt)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC

#+LATEX_HEADER: \usepackage{fontspec}
#+LATEX_HEADER: \setmonofont{Inconsolata}

#+LATEX_HEADER: \usepackage[pdf]{pstricks}

#+LATEX_HEADER: \usepackage[indentfirst=false]{xeCJK}
#+LATEX_HEADER: \setCJKmainfont{WenQuanYi Zen Hei}
#+LATEX_HEADER: \setCJKsansfont{WenQuanYi Zen Hei}
#+LATEX_HEADER: \setCJKmonofont{WenQuanYi Zen Hei}

#+LATEX_HEADER: \usepackage{listings}
#+LATEX_HEADER: \usepackage{color}
#+LATEX_HEADER: \definecolor{codecolor}{RGB}{150,0,100}

#+LATEX_HEADER: 
\newcommand{\inpcode}[1]{\textcolor{codecolor}{\texttt{#1}}}
#+LATEX_HEADER: \newcommand{\codeident}[1]{\mbox{\texttt{#1}}}
#+LATEX_HEADER: \newcommand{\termemph}[1]{\emph{#1}}

#+TITLE:     What's Wrong with Finale? \\ Free Music Notation with LilyPond
#+AUTHOR:    H. James Harkins
# #+DATE:      31 October 2013

#+BEGIN_LaTeX
\AtBeginSection[] % Do nothing for \section*
{
\begin{frame}<beamer>
\frametitle{Outline}
\tableofcontents[currentsection]
\end{frame}
}
#+END_LaTeX
~~



Header of the non-working file:
~~
#+PROPERTY: header-args:lilypond :prologue \header{tagline=##f}

#+TITLE: Notes on the fall 2013 show
#+DATE: <2013-11-27>
#+AUTHOR: James Harkins
#+OPTIONS: ':t *:t -:t ::t <:t H:3 \n:nil ^:t arch:headline author:t
#+OPTIONS: c:nil creator:comment d:(not LOGBOOK) date:t e:t email:nil
#+OPTIONS: f:t inline:t num:t p:nil pri:nil stat:t tags:t tasks:t
#+OPTIONS: tex:t timestamp:t toc:nil todo:t |:t
#+CREATOR: Emacs 23.3.1 (Org mode 8.2)
#+DESCRIPTION:
#+EXCLUDE_TAGS: noexport
#+KEYWORDS:
#+LANGUAGE: en
#+SELECT_TAGS: export

#+OPTIONS: texht:t
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: [a4paper]
#+LATEX_HEADER:
#+LATEX_HEADER_EXTRA:

#+LATEX_HEADER: \usepackage{fontspec}
#+LATEX_HEADER: \setmainfont[Ligatures={Common,TeX}]{CharisSIL}
#+LATEX_HEADER: \setmonofont{Inconsolata}
#+LATEX_HEADER: \setcounter{secnumdepth}{0}

#+LATEX_HEADER: 
\usepackage[a4paper,inner=2.5cm,outer=2.5cm,top=2.8cm,bottom=2.8cm]{geometry}

#+LATEX_HEADER: \usepackage[english]{babel}
~~

Re: #+PROPERTY: for babel header args worked... then it didn't

[Sebastien Vauban]

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

Re: #+PROPERTY: for babel header args worked... then it didn't

[Achim Gratz]

James Harkins writes:
> 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*. 
> ??

Did you C-c C-c the configuration lines (or reverted the document)?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: #+PROPERTY: for babel header args worked... then it didn't

[James Harkins]

Achim Gratz <Stromeko <at> nexgo.de> writes:

> James Harkins writes:
> > 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*. 
> > ??
> 
> Did you C-c C-c the configuration lines (or reverted the document)?

Argh... that must have been it. No, I didn't.

Out of curiousity, will C-c also work for "#+startup: beamer" lines?
"Refresh setup current buffer" is kind of annoying :)

Re: Sebastian's question, it couldn't be a regression. I rendered the beamer
document on Wednesday, no problem, and created the problem document on
Thursday. No git updates in between.

I'm sure Achim's answer is what I missed.

hjh

Re: #+PROPERTY: for babel header args worked... then it didn't

[Sebastien Vauban]

James Harkins wrote:
> Achim Gratz <Stromeko <at> nexgo.de> writes:
>> James Harkins writes:
>> > 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*. 
>> > ??
>> 
>> Did you C-c C-c the configuration lines (or reverted the document)?
>
> Argh... that must have been it. No, I didn't.
>
> Out of curiousity, will C-c also work for "#+startup: beamer" lines?
> "Refresh setup current buffer" is kind of annoying :)
>
> Re: Sebastian's question, it couldn't be a regression. I rendered the beamer
> document on Wednesday, no problem, and created the problem document on
> Thursday. No git updates in between.
>
> I'm sure Achim's answer is what I missed.

I'm sure I did C-c C-c the options. Now, if it does work, it'll prove I still
must be wrong...

Best regards,
  Seb

-- 
Sebastien Vauban