From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Van L <van@scratch.space>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: C++ is not accepted for SRC block evaluation
Date: Sun, 27 May 2018 23:09:23 +0200 [thread overview]
Message-ID: <878t843iws.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87bmd0u8np.fsf@gmail.com> (Aaron Ecay's message of "Sun, 27 May 2018 21:48:42 +0100")
Aaron Ecay <aaronecay@gmail.com> writes:
> Is this right? Even if the feature is provide-d by the file, the require
> in org-babel-do-load-languages will not find it (because the file name
> does not match). C++ is not a valid choice for the variable AFAICT. The
> customize interface makes that clear by not offering it as an option, but
> if the variable is customized outside of customize (so to speak...) chaos
> reigns...
You are right, the change is not sufficient, although it doesn't make
things worse. We could modify `org-babel-load-languages' defcustom and
add lines:
(const :tag "C++" C)
(const :tag "D" C)
which would do the job from Customize, but not for a user changing the
variable outside it, as you point out.
We probably need to implement a mapping between languages symbols and
files and use it in `org-babel-do-load-languages'. The implicit mapping
it uses currently has shortcomings.
We could also leave it like this (even with my patch reverted), and
document it somehow. Maybe a third column per language in (info "(org)
Languages") to hold the file name.
WDYT?
next prev parent reply other threads:[~2018-05-27 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 12:15 C++ is not accepted for SRC block evaluation Van L
2018-05-26 14:50 ` John Kitchin
2018-05-27 2:50 ` Van L
2018-05-27 20:24 ` Nicolas Goaziou
2018-05-27 20:48 ` Aaron Ecay
2018-05-27 21:09 ` Nicolas Goaziou [this message]
2018-05-28 15:57 ` Aaron Ecay
2018-05-30 11:11 ` Nicolas Goaziou
2018-05-30 16:35 ` Berry, Charles
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t843iws.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=van@scratch.space \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.