From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>,
"Berry, Charles" <ccberry@ucsd.edu>
Subject: Re: "header-args :eval inline-only" not working
Date: Sun, 20 Aug 2017 12:21:40 +0200 [thread overview]
Message-ID: <87inhiilor.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <0B21A5BE-80FE-4B83-970B-84C32270BCA3@agrarianresearch.org> (Vikas Rawal's message of "Sun, 20 Aug 2017 08:56:28 +0530")
Hello,
Vikas Rawal <vikaslists@agrarianresearch.org> writes:
> I am on the latest version on org mode ELPA. It is dated August 18,
> 2017, so should include the commit you mention.
`org-export-use-babel' is from "master" branch. ELPA provides "maint".
> But this would prevent exporting all code blocks including inline blocks.
>
> Isn’t it?
>
> There seems no way of separately controlling inline and other blocks.
There is. You put :eval never-export on all src blocks and :eval t on
inline code. Note, however, that inline code might call indirectly src
blocks, so this can lead to odd situations.
What you are missing, probably, is some way to set this globally. Alas,
`org-export-use-babel' or `org-export-babel-evaluate' is not the answer.
As suggested in the thread you mentioned earlier, we might as well get
rid of `org-export-use-babel' altogether. It seems to confuse many users
and isn't very useful.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-08-20 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 16:36 "header-args :eval inline-only" not working Vikas Rawal
2017-08-19 19:27 ` Nicolas Goaziou
2017-08-19 20:36 ` Vikas Rawal
2017-08-19 22:10 ` Berry, Charles
2017-08-20 1:10 ` Vikas Rawal
2017-08-20 2:07 ` Berry, Charles
2017-08-20 2:24 ` Vikas Rawal
2017-08-20 2:43 ` Berry, Charles
2017-08-20 3:26 ` Vikas Rawal
2017-08-20 10:21 ` Nicolas Goaziou [this message]
2017-08-20 12:41 ` Vikas Rawal
2017-08-20 16:51 ` Berry, Charles
2017-08-26 8:34 ` 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=87inhiilor.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=vikaslists@agrarianresearch.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).