From: "Berry, Charles" <ccberry@ucsd.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Van L <van@scratch.space>, org-mode-email <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: C++ is not accepted for SRC block evaluation
Date: Wed, 30 May 2018 16:35:10 +0000 [thread overview]
Message-ID: <D3BFA864-1F6C-4E9B-821E-24D938B0B503@ucsd.edu> (raw)
In-Reply-To: <87d0xd1jq5.fsf@nicolasgoaziou.fr>
> On May 30, 2018, at 4:11 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> Improved documentation is never a bad thing. OTOH, I personally would
>> not spend time on implementing the mapping you propose.
>
> I simply added a footnote about C++ and D languages.
>
>> org-babel-do-load-languages is IMO a relic. I think that all babel
>> languages should be autoloaded, just like normal lisp libraries are.
>
> But we still need a mechanism to selectively allow evaluation of some
> source blocks based on their language. I guess some users expect to have
> this.
>
> Otherwise, it sounds good.
>
>> If I had to sketch a design for this, it would be a macro like:
>>
It would be nice to have a concurrent update to template.el for this scheme.
https://code.orgmode.org/bzg/worg/raw/master/org-contrib/babel/ob-template.el
Chuck
prev parent reply other threads:[~2018-05-30 16:35 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
2018-05-28 15:57 ` Aaron Ecay
2018-05-30 11:11 ` Nicolas Goaziou
2018-05-30 16:35 ` Berry, Charles [this message]
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=D3BFA864-1F6C-4E9B-821E-24D938B0B503@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@nicolasgoaziou.fr \
--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 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).