From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: change in calling remote code blocks?
Date: Mon, 22 Jan 2018 19:44:48 +0100 [thread overview]
Message-ID: <878tcp68db.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJ51ETqRfVWW558BmDRcZneApznCT7xhcAYnzCp=UOC5Bp=3mw@mail.gmail.com> (John Kitchin's message of "Mon, 15 Jan 2018 16:08:26 -0800")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> 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.
Fixed. Thank you. I also updated documentation and added tests.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-01-22 18:44 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
2018-01-22 18:44 ` Nicolas Goaziou [this message]
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=878tcp68db.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).