From: Tim Cross <theophilusx@gmail.com>
To: "numbchild@gmail.com" <numbchild@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Why ob-clojure.el does not respect :dir header argument?
Date: Thu, 29 Jun 2017 12:40:08 +1000 [thread overview]
Message-ID: <CAC=50j-VbwFR722SogW9m5o-UcYfvamatYpxz4E=YoieWH=tTQ@mail.gmail.com> (raw)
In-Reply-To: <CAL1eYuJ_SfSODkqfoaNVmb+LaATZzEgaVtJ+xUSh-SzeWyC+zQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
ob-clojure is limited by what can be done via the interfaces offered by
cider. Have a look at the ob-clojure.el source code - it is very simple and
does not have options/interfaces to support the full range of possible
source block headers. Someone may be able to implement this, but nobody
has. Feel free to have a go at it.
IMO ob-clojure is only written to do very basic clojure code evaluation. If
you want something more complex, you have to add that hyourself.
On 28 June 2017 at 21:01, numbchild@gmail.com <numbchild@gmail.com> wrote:
> In Org-mode Info page, the header argument `:dir` is used to specify the
> default directory for code block execution.
> But `ob-clojure` with `cider` as backend, will always use the
> `cider-jack-in` directory as default working directly. Is there a way to
> change this?
>
> [stardiviner] <Hack this world!> GPG key ID: 47C32433
> IRC(freeenode): stardiviner Twitter: @numbchild
> Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
> Blog: http://stardiviner.github.io/
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 2206 bytes --]
next prev parent reply other threads:[~2017-06-29 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 11:01 Why ob-clojure.el does not respect :dir header argument? numbchild
2017-06-29 2:40 ` Tim Cross [this message]
2017-06-29 5:13 ` numbchild
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='CAC=50j-VbwFR722SogW9m5o-UcYfvamatYpxz4E=YoieWH=tTQ@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.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).