emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: no pdf-output in lilypond code blocks
Date: Wed, 30 Jan 2013 21:32:00 +0100	[thread overview]
Message-ID: <871ud2if9b.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ip6ezzlb.fsf@bzg.ath.cx

Bastien writes:
> Hi Florian,
>
> Florian Beck <fb@miszellen.de> writes:
>
>> 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?
>
> Indeed.  This is now the case, thanks!

This would be a bug, I believe you should use backquotes on the string
constants if indeed pcase should wend its way into Org (this would be
the only place using it):

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

But wouldn't something like

(or (cdr (assoc (file-name-extension out-file)
                '(("pdf" . "--pdf ")
		  ("ps" . "--ps ")
		  ("png" . "--png "))))
    "--png ")

work just as well?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2013-01-30 20:32 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
2013-01-30 11:20         ` Bastien
2013-01-30 20:32           ` Achim Gratz [this message]
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=871ud2if9b.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).