emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: #+call and strange behaviour
Date: Wed, 24 Jun 2020 11:14:23 +0200	[thread overview]
Message-ID: <87k0zwn7v4.fsf@luisa.c0t0d0s0.de> (raw)


in a file named test.org I have an elisp src code block and a line like

#+call: test.org:hcw(d="foo")

C-c C-c on that line executes the code block just fine. Copying the line
to another org file and pressing C-c C-c results in nothing obvious. On
the other hand, putting a code block in this other org file C-cC-c works
as expected again on a line such as this:

#+call: other.org:hcwother(d="foo")

It seems like it doesn't work if one references a code block in a file
that isn't the current/own file of the reference. Any hints on this,


             reply	other threads:[~2020-06-24  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24  9:14 Michael Welle [this message]
2020-06-24  9:27 ` #+call and strange behaviour Michael Welle

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:

  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=87k0zwn7v4.fsf@luisa.c0t0d0s0.de \
    --to=mwe012008@gmx.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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