From: "Thomas S. Dye" <tsd@tsdye.online>
To: emacs-orgmode@gnu.org
Subject: Re: execute src block during export (Re: Worg HTML export problem?)
Date: Fri, 12 Nov 2021 06:55:42 -1000 [thread overview]
Message-ID: <87fss1jott.fsf@tsdye.online> (raw)
In-Reply-To: <smlti4$hqk$1@ciao.gmane.io>
Aloha Max,
Max Nikulin <manikulin@gmail.com> writes:
> On 12/11/2021 00:24, Thomas S. Dye wrote:
>> The original problem is likely due to the default header
>> arguments in
>> ob-org.el, which are unusual.
>
> It is great that the problem is solved. I do not think however
> that something
> inside ob-org.el may affect processing of a file before this
> package is loaded.
>
>> If I export both, then all is well.
>> #+begin_src emacs-lisp :results value none :exports both
>> (org-babel-do-load-languages
>> 'org-babel-load-languages
>> '((org . t)))
>> #+end_src
>
> I feel that I have missed something. I do not see the purpose to
> include this
> source block in user docs. I expect that for accidental usage it
> is more
> convenient to type (require 'ob-org), while as a permanent
> settings it is
> possible to do customize-variable org-babel-load-languages or to
> use
> `add-to-list'.
The source block is included to show the user how to modify their
.emacs.
I was surprised that changing its :results header argument had an
effect on export.
Do you have an explanation why the header argument makes this
difference on Worg?
All the best,
Tom
--
Thomas S. Dye
https://tsdye.online/tsdye
next prev parent reply other threads:[~2021-11-12 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 22:46 Worg HTML export problem? Thomas S. Dye
2021-11-10 16:50 ` Max Nikulin
2021-11-10 21:24 ` Thomas S. Dye
2021-11-11 13:00 ` execute src block during export (Re: Worg HTML export problem?) Max Nikulin
2021-11-11 17:24 ` Thomas S. Dye
2021-11-12 14:26 ` Max Nikulin
2021-11-12 16:55 ` Thomas S. Dye [this message]
2021-11-13 12:17 ` Max Nikulin
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=87fss1jott.fsf@tsdye.online \
--to=tsd@tsdye.online \
--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).