t...@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.