emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Robert Klein <roklein@roklein.de>
To: Aviv <orgmodegmaneFeb14.z.m1@dfgh.net>, emacs-orgmode@gnu.org
Subject: Re: babel stopping export after updating to org 8.3
Date: Tue, 15 Sep 2015 06:35:52 +0200	[thread overview]
Message-ID: <55F7A028.5000408@roklein.de> (raw)
In-Reply-To: <loom.20150915T050946-349@post.gmane.org>

Hi

Aviv wrote:

> Hi! 
> 
> I just upgraded to org 8.3 and am stuck with an export issue.
> 
> When I try to export a file with just "#+begin_src" and " "#+end_src" as the 
> only lines, I get the error 
> "user-error: No language for src block: (unnamed)". 
> 
> It seems like it is calling org-babel-exp-process-buffer -- but there is no 
> reason that I can tell that is being called.  (org-export-babel-evaluate is 
> definitely nil, thought other testing seems to indicate that shouldn't even 
> matter)
> 
> I've tried this in a clean "emacs -q" emacs and there is no issue -- but I 
> still have the issue with an empty init.el! 
> 
> Any idea what could be wrong?  Thanks!
> 
> 

You need to specify a language, e.g.

#+begin_src foo
#+end_src

You can use any string for language.  However, if you export to latex
you want to either

a) use a language the LaTeX `listings' package knows about or

b) map your language string to a language existing in the `listings'
package.


I like to put configuration files in src blocks as language `conf', so I
added the following to my .emacs file:

(add-to-list 'org-latex-listings-langs
               '(conf " "))

That is, I set the `listings' packages language to a blank (empty string
doesn't work) and only generic settings (i.e. no specific language
settings) are used when I tex the file.

HTH

Best regards
Robert

next prev parent reply	other threads:[~2015-09-15  4:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  4:25 babel stopping export after updating to org 8.3 Aviv
2015-09-15  4:35 ` Robert Klein [this message]
2015-09-15  7:55   ` Aviv
2015-09-15  9:21     ` Robert Klein

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=55F7A028.5000408@roklein.de \
    --to=roklein@roklein.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmodegmaneFeb14.z.m1@dfgh.net \
    /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

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).