emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonathan Gregory <jgrg@autistici.org>
To: numbchild@gmail.com
Cc: Oliver Heck <oliver.heck@posteo.de>, emacs-orgmode@gnu.org
Subject: Re: Org-babel-lilypond always renders full pages
Date: Tue, 31 Mar 2020 10:48:41 -0300	[thread overview]
Message-ID: <87h7y463eu.fsf@autistici.org> (raw)
In-Reply-To: <87y2rigz8y.fsf@gmail.com>

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.

[...]

--
Jonathan

  reply	other threads:[~2020-03-31 13:49 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 [this message]
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
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=87h7y463eu.fsf@autistici.org \
    --to=jgrg@autistici.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@gmail.com \
    --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).