emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Florian Beck <fb@miszellen.de>
To: emacs-orgmode@gnu.org
Subject: Re: no pdf-output in lilypond code blocks
Date: Thu, 31 Jan 2013 19:45:38 +0100	[thread overview]
Message-ID: <87sj5h199p.fsf@sophokles.streitblatt.de> (raw)
In-Reply-To: <87ip6duutd.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 31 Jan 2013 18:27:26 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> Achim Gratz writes:
>> 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).
>
> I've looked at this again and I still don't understand the docstring.
> I've confirmed that the bytecompiler produces not only a warning during
> compilation, but the compiled code won't work, 

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

> so despite indications to
> the contrary the backquotes are indeed necessary.  This means that
> either the docstring fails to clearly indicate the necessity of using
> the backquotes on string constants or the bytecompiler fails to compile
> legal code: I'd suggest you take this example to emacs-bugs and see what
> the devs have to say.
>
>
> Regards,
> Achim.

-- 
Florian Beck

  reply	other threads:[~2013-01-31 18:45 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 [this message]
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=87sj5h199p.fsf@sophokles.streitblatt.de \
    --to=fb@miszellen.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).