From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn 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 Message-ID: References: <874mjsq2r7.fsf@nicolasgoaziou.fr> <8737zcoh9r.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSngB-0003A6-Qd for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 10:52:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSngA-0000Tu-MN for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 10:52:27 -0400 Received: from mail-ob0-x22a.google.com ([2607:f8b0:4003:c01::22a]:34848) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSngA-0000To-H8 for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 10:52:26 -0400 Received: by obbwr7 with SMTP id wr7so60678691obb.2 for ; Fri, 21 Aug 2015 07:52:26 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Andreas Leha Cc: emacs-orgmode Mailinglist On Fri, Aug 21, 2015 at 10:43 AM, Andreas Leha wrote: > Hi, > > Ista Zahn writes: >> On Fri, Aug 21, 2015 at 10:20 AM, Nicolas Goaziou >> wrote: >>> Ista Zahn 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 > >