emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "JI, Xiang" <hi@xiangji.me>
To: emacs-orgmode@gnu.org
Subject: Re: "user-error: No language for src block: (unnamed)" when running `org-icalendar-combine-agenda-files`
Date: Thu, 20 Aug 2015 17:44:27 +0800	[thread overview]
Message-ID: <etPan.55d5a17b.5ce8b716.15fbb@Xiangs-MacBook-Pro.local> (raw)
In-Reply-To: <etPan.55d5a015.28e7c5dc.15fbb@Xiangs-MacBook-Pro.local>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

Well actually I think the error shows because of another block below the emacs-lisp blocks. In this header I just wrote #+BEGIN_SRC without any language name. Is it actually wrong and maybe I should have written #+BEGIN_EXAMPLE instead? Though I’d still say it probably shouldn’t have failed the export?…


On 20. August 2015 at 17:38:36, JI, Xiang (hi@xiangji.me) wrote:

I’m trying to export all my agenda files into an ics file via org-icalendar-combine-agenda-files. However, the export process stops halfway through. The following are shown in Messages:

org-babel-exp process emacs-lisp at line 72...
org-babel-exp process emacs-lisp at line 208...
user-error: No language for src block: (unnamed)

which is weird because

I already set org-calendar-include-body to nil. I don’t think a code block in the middle of a org file should impact iCalendar export.
The code block begins with #BEGIN_SRC emacs-lisp and is highlighted correctly. I’m not sure why it says “no language for src block”.
Regards,

JI, Xiang


[-- Attachment #2: Type: text/html, Size: 4731 bytes --]

  reply	other threads:[~2015-08-20  9:44 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 [this message]
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
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=etPan.55d5a17b.5ce8b716.15fbb@Xiangs-MacBook-Pro.local \
    --to=hi@xiangji.me \
    --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).