emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ista Zahn <istazahn@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: "user-error: No language for src block: (unnamed)" when running `org-icalendar-combine-agenda-files`
Date: Fri, 21 Aug 2015 10:52:06 -0400	[thread overview]
Message-ID: <CA+vqiLGMiwsXKNFB7uw1BzPTwr-iZ694idjxgbmdpTiwCt0npA@mail.gmail.com> (raw)
In-Reply-To: <olur3mw4s8c.fsf@med.uni-goettingen.de>

On Fri, Aug 21, 2015 at 10:43 AM, Andreas Leha
<andreas.leha@med.uni-goettingen.de> wrote:
> Hi,
>
> Ista Zahn <istazahn@gmail.com> writes:
>> On Fri, Aug 21, 2015 at 10:20 AM, Nicolas Goaziou
>> <mail@nicolasgoaziou.fr> wrote:
>>> Ista Zahn <istazahn@gmail.com> writes:
>>>
>>>> Unless you've restored sanity by setting org-export-babel-evaluate to
>>>> nil. Personally I think this is not a good default. Source block
>>>> evaluation and export are distinct actions, and I don't see why they
>>>> should be linked by default.
>>>
>>> Wild guess:
>>>
>>> Principle of least surprise: setting it to nil means results from Babel
>>> code are not refreshed before export, without user realizing about it.
>>> I think most users would like them to be up-to-date before export. It
>>> seems sane to me.
>>
>> The problem is that if the code blocks are non-trivial it slows down
>> the export. Changing one line of documentation and exporting
>> re-evaluates all the code blocks, which for me often takes several
>> minutes. The defaults work for trivial examples, but not my real-world
>> use. Since it's easy to make it work how I want it to via
>> org-export-babel-evaluate I don't mean to complain too much. I posted
>> mostly to make sure the OP knows about org-export-babel-evaluate, in
>> case disabling code block evaluation on export makes sense for them.
>>
>
> I know that problem...
>
> Decoupling code block evaluation and export has the problem of
> decoupling code block evaluation and export ;-), though.  If you export
> your document without evaluating first, how can you be sure that the
> resulting document is based on the latest version of the code contained
> in the code blocks?

By calling org-babel-execute-buffer before exporting ;-)

The advantage of doing it this way is that you don't have to do that
if you haven't changed a code block.

  So, from my point of view the default is the safe
> option and, thus, fine.

I agree that it is safer. In my case its safer like a 10 MPH speed
limit. Safe yes, but too slow!

>
>
> Regards,
> Andreas
>
>

  reply	other threads:[~2015-08-21 14:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  9:38 "user-error: No language for src block: (unnamed)" when running `org-icalendar-combine-agenda-files` JI, Xiang
2015-08-20  9:44 ` JI, Xiang
2015-08-21 11:50   ` Nicolas Goaziou
2015-08-21 13:46     ` Ista Zahn
2015-08-21 14:20       ` Nicolas Goaziou
2015-08-21 14:35         ` Ista Zahn
2015-08-21 14:43           ` Andreas Leha
2015-08-21 14:52             ` Ista Zahn [this message]
2015-08-21 15:04               ` Nicolas Goaziou
2015-08-21 15:57                 ` Ista Zahn
2015-08-21 20:13                   ` Aaron Ecay
2015-08-21 20:19                     ` Andreas Leha
2015-08-22  3:19                       ` Charles C. Berry
2015-08-21 20:19                   ` Charles C. Berry

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+vqiLGMiwsXKNFB7uw1BzPTwr-iZ694idjxgbmdpTiwCt0npA@mail.gmail.com \
    --to=istazahn@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --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).