From: Volker Strobel <volker.strobel87@gmail.com>
To: Soapy Smith <soapy-smith@comcast.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Namespace problem org-mode / Clojure
Date: Tue, 25 Feb 2014 10:22:21 +0100 [thread overview]
Message-ID: <87vbw3v96a.fsf@gmail.com> (raw)
In-Reply-To: <1393170060.2128.14.camel@raven-CM5571>
Hi Soapy,
thank you! I feel at ease knowing that you could replicate
the behavior, as I was trying to find the error in my settings for a
long, long time (and as mentioned before, it did work for some time, and
I've no clue why - I've played around with some settings in the init file).
And yes, adding an explicit namespace declaration (ns, in-ns) to every code
block works, but that's a rather roundabout way (I've many small
snippets in the same namespace) and it produces a bit 'unsightly',
tangled code. So, I'd be really glad, if this issue could be processed.
Best, Volker
Soapy Smith <soapy-smith@comcast.net> writes:
> Hi Volker-
>
> I tried the your example code blocks on my system, and I concur with
> most of the behavior you described.
>
> org-babel-execute-buffer does not work, as it comes back with error
> "repl not connected". It did not cause a crash.
> However, if I add explicit namespace declaration to the 2nd block, it
> works! This is true even thought the 3rd block does not(???).
>
> I was thinking back to why I never encountered this problem, and it is
> because I have almost always used an explicit namespace declaration at
> the top of the block. Fortunately, after the first block, you don't
> have to use the optional parameters, includes etc. In your example
>
> (ns environment.my-test)
>
> added to subsequent code blocks you wish to execute in the same
> namespace should be sufficient. I think this should be considered the
> "work-around" until someone can explain what is going on, or, even
> better, can fix this.
>
> I'm the person who updated the worg documentation for Clojure code
> blocks. I'm thinking about adding a list of TODOs at the bottom, as
> there have been some other requests recently to the function behavior.
> This issue definitely will go on the list. Hopefully Bastien is
> monitoring and can comment if this is appropriate to add to the Clojure
> specific worg page (or should it go somewhere else).
>
> Regards,
> Greg
--
Sent with my mu4e
next prev parent reply other threads:[~2014-02-25 9:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 21:22 Namespace problem org-mode / Clojure Volker Strobel
2014-02-21 22:36 ` Thomas S. Dye
2014-02-21 23:33 ` Volker Strobel
2014-02-22 0:49 ` Thomas S. Dye
2014-02-23 15:41 ` Soapy Smith
2014-02-25 9:22 ` Volker Strobel [this message]
2014-02-25 11:20 ` Soapy Smith
2014-02-26 12:22 ` Soapy Smith
2014-02-23 15:19 ` Soapy Smith
2014-02-23 18:14 ` Thomas S. Dye
2014-03-03 12:54 ` Bastien
2014-03-04 2:35 ` Soapy Smith
2014-03-04 13:05 ` Soapy Smith
2014-03-13 15:18 ` Bastien
2014-03-19 14:30 ` Volker Strobel
2014-03-19 23:46 ` Soapy Smith
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=87vbw3v96a.fsf@gmail.com \
--to=volker.strobel87@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=soapy-smith@comcast.net \
/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).