emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: swflint@flintfam.org (Samuel W. Flint)
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-babel-tangle error. org-babel-get-header undefined [8.3.2 (release_8.3.2-317-gbd921f @ /home/swflint/.emacs.d/org-mode/lisp/)]
Date: Thu, 12 Nov 2015 14:18:32 -0500	[thread overview]
Message-ID: <87egfvt4af.fsf@turing.flintfam.org> (raw)
In-Reply-To: <87io57f30j.fsf@kyleam.com> (Kyle Meyer's message of "Thu, 12 Nov 2015 14:09:48 -0500")

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

>>>>> Kyle Meyer writes:

KM> "Samuel W. Flint" <swflint@flintfam.org> writes: [...]

>>> In your org-babel-do-load-languages call, try to changing
>>> 
>>> (sh . t)
>>> 
>>> to
>>> 
>>> (shell . t)
>>> 
>>> -- Kyle
>>> 
>>> 
>> 
>> I went ahead and tried that.  I still get that error.

KM> Hmm, and that was after Emacs was restarted?

Nope.  Should have thought of that.  Figures.  That'll probably be all
that it is.

Thanks.

Sam

KM> Here is why I suggested that.  As of Org 8.2, ob-sh was renamed to
KM> ob-shell.  The NEWS file contained this:

KM>     *** =ob-sh.el= renamed to =ob-shell= This may require two
KM> changes in user config.
    
KM>     1. In =org-babel-do-load-languages=, change =(sh . t)= to
KM> =(shell . t)=.  2. Edit =local.mk= files to change the value of
KM> =BTEST_OB_LANGUAGES= to remove "sh" and include "shell".

KM> If you didn't do this (as I didn't), you wouldn't necessarily
KM> notice, because org-babel-do-load-languages ends up loading the old
KM> ob-sh.el that ships with Emacs.  As the builtin ob-sh.el and babel
KM> diverged, there were very likely subtle and perhaps not-so-subtle
KM> bugs, but the blocks would execute until recently.  Execution now
KM> fails because org-babel-get-header was removed in 0d000f5 (babel:
KM> small change in API., 2015-10-29), but the old ob-sh.el is still
KM> trying to call it.

KM> Based on the configuration you included, you do need to change (sh
KM> . t) to (shell . t), but perhaps there is still some other issue
KM> going on.  If a restart with the previous suggestion doesn't fix it,
KM> please try to put together a minimal Org file and configuration that
KM> will reproduce the issue with emacs -Q.

KM> -- Kyle 

-- 
Samuel W. Flint
4096R/266596F4
      (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

      reply	other threads:[~2015-11-12 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 17:24 Bug: org-babel-tangle error. org-babel-get-header undefined [8.3.2 (release_8.3.2-317-gbd921f @ /home/swflint/.emacs.d/org-mode/lisp/)] Samuel W. Flint
2015-11-12 17:36 ` Kyle Meyer
2015-11-12 18:41   ` Samuel W. Flint
2015-11-12 19:06     ` Nick Dokos
2015-11-12 19:09     ` Kyle Meyer
2015-11-12 19:18       ` Samuel W. Flint [this message]

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=87egfvt4af.fsf@turing.flintfam.org \
    --to=swflint@flintfam.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    /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).