From: "Victor A. Stoichita" <victor@svictor.net>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: [BUG?] org-babel-lilypond-commands can't be set through customize
Date: Mon, 10 Feb 2020 10:44:45 +0100 [thread overview]
Message-ID: <874kvyydwy.fsf@svictor.net> (raw)
Hi!
In ob-lilypond the variable org-babel-lilypond-commands appears to
be in a weird state. The customize interface says:
> org-babel-lilypond-commands: nil
> [ State ]: UNKNOWN, you should not see this.
> Commands to run lilypond and view or play the results.
> These should be executables that take a filename as
> an argument.
> On some system it is possible to specify the filename
> directly
> and the viewer or player will be determined from the file
> type;
> you can leave the string empty on this case.
[C-h v] says:
> org-babel-lilypond-commands is a variable defined in
> ‘ob-lilypond.el’.
> It is void as a variable.
I can't set the variable through customize. I don't know what the
syntax would be to set it with setq.
Actually I only need to customize the more specific
org-babel-lilypond-midi-command. I can set this one with something
like
(setq org-babel-lilypond-midi-command "timidiy").
However its docstring says:
> org-babel-lilypond-midi-command is a variable defined in
> ‘ob-lilypond.el’.
> Its value is "timidity"
> This variable may be risky if used as a file-local variable.
> Documentation:
> Command to play a MIDI file on your system.
> Do not set it directly.
> Customize ‘org-babel-lilypond-commands’ instead.
Hence my attempt to customize org-babel-lilypond-commands.
I have org-mode 9.3.1.
Regards,
Victor
next reply other threads:[~2020-02-10 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 9:44 Victor A. Stoichita [this message]
2020-02-11 7:52 ` [BUG?] org-babel-lilypond-commands can't be set through customize 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=874kvyydwy.fsf@svictor.net \
--to=victor@svictor.net \
--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).