> On May 30, 2018, at 4:11 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> Aaron Ecay 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-
Hello,
Aaron Ecay 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 sh
Hi Nicolas,
2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen:
[...]
>
> 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
Aaron Ecay 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 offerin
Hi Nicolas,
2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen:
[...]
> No, that's not correct. It should be (C++ . t), but "ob-C.el" should
> provide "ob-C++" feature, too.
Is this right? Even if the feature is provide-d by the file, the require
in org-babel-do-load-languages will not find
Hello,
Van L writes:
>> John Kitchin writes:
>>
>> It should be (C . t)
>>
>> it looks like ob-C also handles C++.
>
> How about the following to update the documentation:
>
> #+BEGIN_EXAMPLE
> diff --git a/doc/misc/org.texi b/doc/misc/org.texi
> index cf1c037..7b00f0a 100644
> --- a/doc
> John Kitchin writes:
>
> It should be (C . t)
>
> it looks like ob-C also handles C++.
> Section 14.7 Languages in the Org Mode working with source code infopages
> lists C++.
Thanks.
How about the following to update the documentation:
#+BEGIN_EXAMPLE
diff --git a/doc/misc/org.texi b/d
It should be (C . t)
it looks like ob-C also handles C++.
John
---
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Sat, Ma
Hello.
The `m-x customize’ path to `org-babel-load-languages’ or the following method
won’t accept C++.
#+BEGIN_SRC elisp :results none
(org-babel-do-load-languages
'org-babel-load-languages
'((C++ . t)))
#+END_SRC
The messages buffer has the following.
executing Elisp code block...