emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Org-babel-lilypond always renders full pages


From: stardiviner
Subject: Re: Org-babel-lilypond always renders full pages
Date: Thu, 02 Apr 2020 16:35:05 +0800
User-agent: mu4e 1.3.8; emacs 28.0.50

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Jonathan Gregory <address@hidden> writes:

> Hi
>
> On 30 Mar 2020, stardiviner <address@hidden> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>> stardiviner <address@hidden> writes:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>>
>>> You might want to try this:
>>>
>>> #+begin_src emacs-lisp
>>> (add-to-list 'org-babel-default-header-args:lilypond
>>>              '((:prologue . "\paper{
>>>   indent=0\mm
>>>   line-width=120\mm
>>>   oddFooterMarkup=##f
>>>   oddHeaderMarkup=##f
>>>   bookTitleMarkup = ##f
>>>   scoreTitleMarkup = ##f
>>> }")))
>>> #+end_src
>>>
>>
>> I found this custom setting lilypond header arguments will not work. Because 
>> this code function:
>>
>> #+begin_src emacs-lisp
>> (defun org-babel-lilypond-get-header-args (mode)
>>   "Default arguments to use when evaluating a lilypond source block.
>> These depend upon whether we are in Arrange mode i.e. MODE is t."
>>   (cond (mode
>>          '((:tangle . "yes")
>>            (:noweb . "yes")
>>            (:results . "silent")
>>            (:cache . "yes")
>>            (:comments . "yes")))
>>         (t
>>          '((:results . "file")
>>            (:exports . "results")))))
>>
>> (defun org-babel-lilypond-set-header-args (mode)
>>   "Set org-babel-default-header-args:lilypond
>> dependent on ORG-BABEL-LILYPOND-ARRANGE-MODE."
>>   (setq org-babel-default-header-args:lilypond
>>         (org-babel-lilypond-get-header-args mode)))
>> #+end_src
>>
>> It always reset and return one result of two conditions.
>>
>> I think this is a bug.
>
> So are all org-babel-default-header-args:LANG custom variables? In the
> ob-lilypond.el library the headers are hard-coded.
>
> [...]

Yes, it's hard-coded in that function definition. So setting that header
arguments variable will not work at all.

- -- 
[ stardiviner ]
       I try to make every word tell the meaning what I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
      
-----BEGIN PGP SIGNATURE-----

iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl6Fo7oUHG51bWJjaGls
ZEBnbWFpbC5jb20ACgkQG13xyVromsP2cQf7Bj8/dS+k/P5Hu5sF9gccS8mzrIWL
aLrJ/lFtkkwP7IbAUTYxW3zNAISHSa285oCha2gWzqT8Vc2Vv/NIhpwVKOvq5Ifg
L9FRQuftP3hHekdVAcSwPFMV0ejXPI3vItCzgDhk1+G3BcMwphW37LfOT5v0Sj0D
47cGBhgobPhX4Q3vtPonCdtSgt+bhEsi0Xxa+uNmfhOEEhVflEgvcSLcXtPs5cuv
zkUZhJXCmPx/qFlMT0DphsGk/KLX/NXTfLFQvZ0lA30Vl2Hypnsa6L32MIlZZJOU
rIRgYOwGsFxCCSZfRm6SosVhSApZmJCR9BbjPwVYOlnScJJr8uXsw9ofTA==
=cyEM
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]