From: Bastien <bzg@gnu.org>
To: North Year <ny-ml@outlook.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: org-babel: how to evaluate code block with "alias" language?
Date: Wed, 23 Nov 2022 21:35:36 +0100 [thread overview]
Message-ID: <875yf54dev.fsf@gnu.org> (raw)
In-Reply-To: <MW4PR14MB53277E939B4895089429B4D3E70D9@MW4PR14MB5327.namprd14.prod.outlook.com> (North Year's message of "Tue, 22 Nov 2022 15:29:02 -0500")
Hi North,
North Year <ny-ml@outlook.com> writes:
> #+begin_src emacs-lisp
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((r . t)))
> #+end_src
I suggest you try with an uppercase "R":
#+begin_src emacs-lisp
(org-babel-do-load-languages
'org-babel-load-languages
'((R . t)))
#+end_src
If Org's documentation is not accurate about this, please report a bug
with M-x org-submit-bug-report RET.
--
Bastien
next prev parent reply other threads:[~2022-11-23 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 20:29 org-babel: how to evaluate code block with "alias" language? North Year
2022-11-23 20:35 ` Bastien [this message]
2022-11-24 2:03 ` North Year
2022-11-24 5:23 ` tomas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yf54dev.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=ny-ml@outlook.com \
/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.
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).