From: Alexandre Duret-Lutz <adl@lrde.epita.fr>
To: emacs-orgmode@gnu.org
Subject: Re: #+PROPERTY: header-args:C++ will not work
Date: Mon, 15 Apr 2019 16:08:55 +0200 [thread overview]
Message-ID: <CA+Xfj9R0HcpMkxfOL5N0P3OD9iHkM9YPSRD5bS7MWc1NJh2B4w@mail.gmail.com> (raw)
In-Reply-To: <CA+Xfj9TmrvUvxucSLqNEOGo4ERUTq_0e=Mn9fj+6uwpaVeDwbw@mail.gmail.com>
On Mon, Apr 15, 2019 at 2:53 PM Alexandre Duret-Lutz <adl@lrde.epita.fr> wrote:
> Unfortunately, this does not work for C++ blocks.
I just noticed that I could change all my C++ blocks into cpp blocks and
then use header-args:cpp without any problem. The org-mode manual
states that the identifier for the C++ language is "C++"
(https://orgmode.org/manual/Languages.html) but the same page links to
some babel documentation
(https://orgmode.org/worg/org-contrib/babel/languages.html)
where it is listed as "cpp".
ORG-NEWS has one example using C++, but the test suite only has cpp examples.
There is some hint on
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-C.html#orgea7b004
that using cpp might not fully work (?). And clearly while lisp/org-src.el has
many functions implemented for both cpp and C++, its not always complete.
For instance it defines org-babel-header-args:C++
but there is no org-babel-header-args:cpp, meaning incomplete completion for
cpp blocks header-args.
From all that it feels like the documentation wants us to use C++, and that
the code is trying to keep cpp for backward compatibility (?), but that each
option has different drawbacks.
I'll stick to C++ and header-args:C+++...
--
Alexandre Duret-Lutz
next prev parent reply other threads:[~2019-04-15 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 12:53 #+PROPERTY: header-args:C++ will not work Alexandre Duret-Lutz
2019-04-15 14:08 ` Alexandre Duret-Lutz [this message]
2019-04-23 8:28 ` Nicolas Goaziou
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=CA+Xfj9R0HcpMkxfOL5N0P3OD9iHkM9YPSRD5bS7MWc1NJh2B4w@mail.gmail.com \
--to=adl@lrde.epita.fr \
--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).