From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: no pdf-output in lilypond code blocks
Date: Thu, 31 Jan 2013 20:07:25 +0100 [thread overview]
Message-ID: <87a9rpuq6q.fsf@Rainer.invalid> (raw)
In-Reply-To: 87sj5h199p.fsf@sophokles.streitblatt.de
Florian Beck writes:
> I cannot reproduce this. The code works for me and byte compiling
> doesn't generate any warning.
>
> GNU Emacs 24.3.50.7 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.0) of 2013-01-28 on flo-laptop
Fail: 24.2 (unknown upattern),
23.[34] (malformed function),
22.3 (malformed function)
Pass: 24.3.50, 24.2.9[012]
So it seems to have been fixed by the macro compilation changes that
Stefan Monnier did some months ago.
For grins the result with the backquotes:
Fail: 23.[34] (old-style backquote warning)
22.3 (old-style backquote warning)
Pass: 24.3.50, 24.2.9[012], 24.2
Still not a good idea to use pcase in code that should be backwards
compatible…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-01-31 19:07 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
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 [this message]
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=87a9rpuq6q.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).