From: Michael Albinus <michael.albinus@gmx.de>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Local variables and babel
Date: Tue, 14 Jan 2014 21:38:45 +0100 [thread overview]
Message-ID: <87ha96ti22.fsf@gmx.de> (raw)
In-Reply-To: <m1eh4axt4p.fsf@poto.myhome.westell.com> (Thomas S. Dye's message of "Tue, 14 Jan 2014 09:25:58 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
Hi,
> This led me to try to incorporate some of the file-specific setup steps
> into the local variables as well. For instance, in a file where I'm
> working with Common Lisp source code blocks and a graph library, I have
> this:
>
> # eval: (slime)
> # eval: (org-sbe "graph-setup")
>
> What I've found is that the graph-setup doesn't have any effect on the
> Common Lisp environment when run this way. It works fine if, after slime
> is up and running, I go to the graph-setup source code block and
> evaluate it with C-c C-c.
>
> I'm guessing that I might be running into a concurrency problem here,
> such that the local variable evaluation of graph-setup is taking place
> before slime has finished setting itself up (which takes many seconds on
> my machine).
>
> I am well beyond my programming abilities here and would like to have
> opinions on whether this approach is potentially workable and, if so,
> how it might be implemented.
I don't know slime, but usual there are hooks where you could add your
code to run once a package (like slime) has finished its
initialization. Look for such a hook in slime, and add the call to
graph-setup there.
> All the best,
> Tom
Best regards, Michael.
prev parent reply other threads:[~2014-01-14 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:25 Local variables and babel Thomas S. Dye
2014-01-14 20:38 ` Michael Albinus [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=87ha96ti22.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).