emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: change in calling remote code blocks?
Date: Mon, 15 Jan 2018 16:08:26 -0800	[thread overview]
Message-ID: <CAJ51ETqRfVWW558BmDRcZneApznCT7xhcAYnzCp=UOC5Bp=3mw@mail.gmail.com> (raw)
In-Reply-To: <87r2qqybxp.fsf@nicolasgoaziou.fr>

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

I don't recall how I learned about that, I guess maybe in some library of
babel documentation somewhere. I confirmed it does work in 8.2.10, e.g.
just with emacs -Q.

There are a few changes in org 9 to org-babel-lob-execute-maybe
and org-babel-lob-get-info that seem to be the root cause of the change.
Notably, org-babel-lob-get-info now returns nil where it used to return the
"path" to the file and block.

So, if I put this into an org file

(progn
 (re-search-forward "call")
 (message "%s" (org-babel-lob-get-info)))   ;<- execute here


#+call: remote-call.org:test-block()

These get returned

In 8.2.10: "(remote-call.org:test-block() nil 0 nil)"
In 9.1.6: "nil"

I am not sure what all the differences are, but it seems to be where the
change in behavior came from.

John

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


On Mon, Jan 15, 2018 at 2:49 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > In org8 I used to be able to call remote code blocks (
> > http://kitchingroup.cheme.cmu.edu/blog/2016/02/09/Calling-
> remote-code-blocks-in-org-mode/
> > )
> >
> > with a syntax like:
> >
> > #+call: si.org:figure-1() :wrap html
> >
> > And C-c C-c on that line would call a code block named figure-1 in the
> file
> > si.org and insert the results.
> >
> > in org 9.1.6, this does nothing. Does anyone know if this got changed,
> and
> > if there is a new way to do that?
>
> This sounds like a bug.
>
> It does ring a bell. However, I couldn't find any reference to this
> syntax or behaviour in the manual. Am I missing something?
>
> Regards,
>
> --
> Nicolas Goaziou
>

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

  reply	other threads:[~2018-01-16  0:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 18:07 change in calling remote code blocks? John Kitchin
2018-01-15 22:49 ` Nicolas Goaziou
2018-01-16  0:08   ` John Kitchin [this message]
2018-01-22 18:44     ` Nicolas Goaziou
2018-01-22 19:24       ` Nicolas Goaziou
2018-01-23  4:36         ` numbchild
     [not found] <mailman.107.1516122017.10361.emacs-orgmode@gnu.org>
2018-01-18  5:48 ` edgar

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='CAJ51ETqRfVWW558BmDRcZneApznCT7xhcAYnzCp=UOC5Bp=3mw@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).