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 22:29:16 +0100 [thread overview]
Message-ID: <87sj5igy1f.fsf@Rainer.invalid> (raw)
In-Reply-To: 874nhy2xm3.fsf@sophokles.streitblatt.de
Florian Beck writes:
> I don't think so. The string evaluates to itself or am I missing
> something?
If it would fall under "SELFQUOTING" then yes (but I really don't
understand what the doc string is trying to tell me there and what would
be used for comparison). It seems that a string constant is not
self-quoting during compilation (the byte-compiler complains about an
"Unknown upattern `pdf'"), most likely due to the pre-expansion of the
macro before compilation. Also the string constant "pdf" compiled ionto
the code can not necessarily match itself when compared to a string
stored in a variable, although at least in interpretation mode this
works. On the other hand a backquoted QPattern where QPattern is a
STRING(constant) does use "equal" for comparison and this is what we
want, plus the bytecompiler seems to like that form better than the
first.
Anyway, pcase is nice when you need it, but in this case I'm not
convinced its worth the trouble. It doesn't even put enough syntactic
sugar on it to make the code more readable.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2013-01-30 21:29 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 [this message]
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=87sj5igy1f.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).