From: Vicente Vera <vicentemvp@gmail.com>
To: Vicente Vera <vicentemvp@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Export backends are loaded after code block evaluation
Date: Mon, 24 Nov 2014 15:45:27 -0300 [thread overview]
Message-ID: <CAMfbzvCdP0JNWN8dHTmpAnb+hOH_eELu0NTYdk7vT5pOBqT4Vg@mail.gmail.com> (raw)
In-Reply-To: <877fyl50y0.fsf@nicolasgoaziou.fr>
Nope, no harm has been done. Still curious about it though. IMO,
there's no reference to 'ox.el' in the babel source files so I don't
understand how is this possible.
2014-11-23 13:36 GMT-03:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Hello,
>
> Vicente Vera <vicentemvp@gmail.com> writes:
>
>> Hello. Just noticed that after evaluating a code block with C-c C-c
>> (org-babel-execute-src-block?) all export backends stored in
>> 'org-export-backends' are loaded---or 'required'---automatically. Once
>> I commented out my 'org-export-backends' setup those backends weren't
>> loaded, but the default ones did (ascii html icalendar latex).
>>
>> Is this the intended behavior?
>
> `org-babel-execute-src-block' probably requires "ox.el" or some
> back-end, triggering. Back-ends are loaded as soon as "ox.el" is
> required.
>
>> Tried to grep my way through Org's source files looking for a clue
>> with no success.
>>
>> Also, is there a way to prevent this from happening? It doesn't seem
>> extremely necessary to me.
>
> It doesn't really hurt either.
>
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2014-11-24 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:57 Export backends are loaded after code block evaluation Vicente Vera
2014-11-23 16:36 ` Nicolas Goaziou
2014-11-24 18:45 ` Vicente Vera [this message]
2014-11-24 19:42 ` Nicolas Goaziou
2014-11-25 0:30 ` Vicente Vera
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=CAMfbzvCdP0JNWN8dHTmpAnb+hOH_eELu0NTYdk7vT5pOBqT4Vg@mail.gmail.com \
--to=vicentemvp@gmail.com \
--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).