From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: #+call and strange behaviour
Date: Wed, 24 Jun 2020 11:27:13 +0200 [thread overview]
Message-ID: <87imfgizke.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <87k0zwn7v4.fsf@luisa.c0t0d0s0.de> (Michael Welle's message of "Wed, 24 Jun 2020 11:14:23 +0200")
Hello again,
sorry, for the noise. Just minutes after posting the question I
discovered the difference between the org files: they are stored in
different sub-directories. Fixing the path solved my problem:
#+call: ../test.org:hcw(d="foo")
Seems like rubber ducking kind of works ;).
Regards
hmw
prev parent reply other threads:[~2020-06-24 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 9:14 #+call and strange behaviour Michael Welle
2020-06-24 9:27 ` Michael Welle [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=87imfgizke.fsf@luisa.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--cc=emacs-orgmode@gnu.org \
/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).