emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Oliver Heck <oliver.heck@posteo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org-babel-lilypond always renders full pages
Date: Mon, 30 Mar 2020 08:55:09 +0200	[thread overview]
Message-ID: <ec57bf6e-e6f4-fead-a7b7-880e5d9c5ad3@posteo.de> (raw)
In-Reply-To: <87mu7y7lyb.fsf@autistici.org>

Actually it is sufficient to have
   \paper{ oddFooterMarkup=##f }
for my needs.

But now I get the rendered pictures very large in the LaTeX-PDF export. 
I added
   (setq org-latex-image-default-width "")
to my .spacemacs file but that does not change anything.

I am quite new to emacs so please excuse my beginner questions.

Thanks,
Oliver

On 30.03.20 01:58, Jonathan Gregory wrote:
> Hi
> 
> On 29 Mar 2020, Oliver Heck <oliver.heck@posteo.de> wrote:
> 
>> Hi,
>>
>> I am trying to use org-babel-lilypond and basically got it running.
>> But somehow I always get full lilypond pages back instead of a small
>> snippet.
>> This is what I have in my org-file:
>>
>> #+NAME: Lilypond
>> #+BEGIN_SRC lilypond :file test.png
>>    \relative c'' { c d e f }
>> #+END_SRC
>>
>>
>> I read through the documentation on
>> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html
>> but cannot find a clue.
>>
>> Any idea what I am doing wrong here?
>>
>> Cheers,
>> Oliver
> 
> The lilypond manual suggests using \paper variables to reduce the white
> space around the score. In particular, you should set oddFooterMarkup
> and oddHeaderMarkup to false.
> 
> \paper{
>    indent=0\mm
>    line-width=120\mm
>    oddFooterMarkup=##f
>    oddHeaderMarkup=##f
>    bookTitleMarkup = ##f
>    scoreTitleMarkup = ##f
> }
> 
> http://lilypond.org/doc/v2.18/Documentation/usage/lilypond-output-in-other-programs
> 
> --
> Jonathan
> 

-- 
--
If you are thinking without writing, you only think you are thinking. 
(Leslie Lamport)

      parent reply	other threads:[~2020-03-30  6:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 21:11 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
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 [this message]

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=ec57bf6e-e6f4-fead-a7b7-880e5d9c5ad3@posteo.de \
    --to=oliver.heck@posteo.de \
    --cc=emacs-orgmode@gnu.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).