emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Florian Beck <fb@miszellen.de>
To: Bastien <bzg@altern.org>
Cc: Florian Beck <fb@miszellen.de>, emacs-orgmode@gnu.org
Subject: Re: no pdf-output in lilypond code blocks
Date: Sat, 26 Jan 2013 17:53:38 +0100	[thread overview]
Message-ID: <877gmzsx65.fsf@sophokles.streitblatt.de> (raw)
In-Reply-To: <87libg6wen.fsf@bzg.ath.cx> (Bastien's message of "Sat, 26 Jan 2013 12:01:04 +0100")

Bastien <bzg@altern.org> writes:

> Hi Florian,
>
> Florian Beck <fb@miszellen.de> writes:
>
>>> If so, I'll fix ly-process-basic so that it depends on
>>> ly-gen-png/pdf/html/svg.
>>>
>>> Thanks for confirming,
>>
>> Thanks for fixing.
>
> Done -- please have a try and let me know.

Minor hitch: the variable is called `ly-use-eps' not `ly-gen-eps'.

However, as far as I understand these variables are intended for tangled
files. The original bug was that exporting or evaluating a code
block doesn't respect the extension of the :file directive.

I can live with setting `ly-gen-pdf', but maybe something like

(pcase (file-name-extension out-file)
        ("pdf" "--pdf ")
        ("ps" "--ps ")
        ("png" "--png ")
        (t "--png "))

would be even better?


-- 
Florian Beck

  reply	other threads:[~2013-01-26 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 13:51 no pdf-output in lilypond code blocks Florian Beck
2013-01-23 14:38 ` Bastien
2013-01-25  9:28   ` Florian Beck
2013-01-26 11:01     ` Bastien
2013-01-26 16:53       ` Florian Beck [this message]
2013-01-30 11:20         ` Bastien
2013-01-30 20:32           ` Achim Gratz
2013-01-30 21:02             ` Florian Beck
2013-01-30 21:29               ` Achim Gratz
2013-01-31 17:27                 ` Achim Gratz
2013-01-31 18:45                   ` Florian Beck
2013-01-31 19:07                     ` Achim Gratz
2013-01-31 10:17             ` Bastien

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=877gmzsx65.fsf@sophokles.streitblatt.de \
    --to=fb@miszellen.de \
    --cc=bzg@altern.org \
    --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).