emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: Jonathan Gregory <jgrg@autistici.org>
Cc: Oliver Heck <oliver.heck@posteo.de>, emacs-orgmode@gnu.org
Subject: Re: Org-babel-lilypond always renders full pages
Date: Thu, 02 Apr 2020 16:35:05 +0800	[thread overview]
Message-ID: <87wo6ymgjq.fsf@gmail.com> (raw)
In-Reply-To: <87h7y463eu.fsf@autistici.org>

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


Jonathan Gregory <jgrg@autistici.org> writes:

> Hi
>
> On 30 Mar 2020, stardiviner <numbchild@gmail.com> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>>
>> stardiviner <numbchild@gmail.com> 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-----

  parent reply	other threads:[~2020-04-02  8:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 21:11 Org-babel-lilypond always renders full pages Oliver Heck
2020-03-29 23:58 ` Jonathan Gregory
2020-03-30  4:34   ` Oliver Heck
2020-03-30  5:35     ` stardiviner
2020-03-30  5:54       ` Oliver Heck
2020-03-30  5:58       ` stardiviner
2020-03-31 13:48         ` Jonathan Gregory
2020-03-31 21:36           ` adam
2020-04-01  9:02             ` Oliver Heck
2020-04-01 23:23               ` adam
2020-04-02  8:35           ` stardiviner [this message]
2020-04-02 22:56             ` Jonathan Gregory
2020-04-05  3:10               ` stardiviner
2020-04-06 21:39                 ` Nick Dokos
2020-03-31 13:43     ` Jonathan Gregory
2020-03-31 14:54       ` Oliver Heck
2020-03-30  6:55   ` Oliver Heck

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=87wo6ymgjq.fsf@gmail.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jgrg@autistici.org \
    --cc=oliver.heck@posteo.de \
    /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).