emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Joon Ro <joon.ro@outlook.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: v9.0 running babel blocks
Date: Thu, 03 Nov 2016 19:50:28 -0400	[thread overview]
Message-ID: <m2ins486nv.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <CY1PR15MB0534FF5CC5812804B2393E69EBA30@CY1PR15MB0534.namprd15.prod.outlook.com>

huh.. it seems to have disappeared. I deleted the orgplus directory in
my elpa directory and reinstalled it, and it seemed to go away.

weird.

Joon Ro writes:

>> I get this message on trying to run an elisp block.
>>
>> Evaluation of this emacs-lisp code-blockis disabled.
>>
>>
>> There are two issues:
>> 1. there is a missing space between block and is (and maybe code-block
>> should not be hyphenated) in org-babel-check-evaluate
>> 2. It used to work! If I run (org-babel-check-confirm-evaluate
>> (org-babel-get-src-block-info)) in the code block, it returns t
>>
>>
>> I am not sure what is causing it. Thoughts?
>
> I'm having exactly the same issue after upgrading to 9.0.
>
>
> In my case, the source code block has a name, and it says "Evaluation of this shell code-block (name) is disabled", so I guess the missing space issue happens when the code block does not have name.
>
>
> Best,
>
> Joon


-- 
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

  reply	other threads:[~2016-11-03 23:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 19:50 v9.0 running babel blocks John Kitchin
2016-11-03 21:47 ` Joon Ro
2016-11-03 23:50   ` John Kitchin [this message]
2016-11-04  2:40     ` Joon Ro
2016-11-22 15:46     ` Alan Schmitt
2016-11-23  7:48       ` Alan Schmitt
2016-11-28  8:01         ` Alan Schmitt
2016-11-28 10:54           ` Alan Schmitt
2016-11-28 13:51             ` Ista Zahn
2016-11-29  9:26               ` Alan Schmitt
2016-11-04  7:37 ` Nicolas Goaziou

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=m2ins486nv.fsf@Johns-MacBook-Air.local \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=joon.ro@outlook.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).