Update: I just got back from vacation and have done a fresh git clone, et all (including updating VB to 4.1.0). I still get the same issue: No error, but a "hang" at Installed Jark (I say hang because the terminal shell is stuck running the vagrant script where I would assume it would have returned once the VM was successfully running).
I opened a new terminal window and ran the clojure_emacs.sh script manually. Unlike last time, this seems to have worked but requied a logout and back in to get jark running and emacs to connect. From there things seems ok. However, vagrant halt didn't do anything (but hang the shell) and I was forced to shutdown manually from inside the vm (sudo shutdown now). I did a vagrant up again and it is setting up a brand new VM for me. Not sure what it did with the old VM or why it insists on creating a new one. If this run doesn't work then I will send all the output to a file and send that to you so you can see if anything seems amiss. Thanx, joe P.S. The current git repo requires at least VB 4.1.0, but the actual image it downloads throws a warning up about the VB Extensions not matching. The VM still has 4.0.6 extensions installed on it. On Sat, Jul 9, 2011 at 10:16 AM, Stan Dyck <stan.d...@gmail.com> wrote: > Another thing to try is this: > > 1. Bring up the vm with a vagrant up > 2. Log in with vagrant ssh > 3. Run the /vagrant/clojure_emacs.sh script directly on the vm > > That might not work either, but at least you'll get some feedback about > what fails from the script output. I'm curious about why it's failing so let > me know if you find out. > > StanD. > > > On 07/08/2011 10:47 PM, Joseph Jones wrote: > >> Still no love. Same thing, only this time there wasn't even an empty >> .emacs.d folder. >> >> On Fri, Jul 8, 2011 at 10:51 AM, Joseph Jones >> <darkdescend...@gmail.com<mailto: >> darkdescendant@gmail.**com <darkdescend...@gmail.com>>> wrote: >> >> When I tried bringing it down and back up, it restarted the whole >> process over from scratch. Basically, vagrant halt >> seems to cause the entire VM to disappear as if vagrant destroy was >> called. :-( >> >> I'll try to re-get from git and see if it works better now. >> >> >> On Fri, Jul 8, 2011 at 9:30 AM, Stan Dyck <stan.d...@gmail.com<mailto: >> stan.d...@gmail.com>> wrote: >> >> There was a minor bug in the provisioning script that prevented the >> .emacs.d directory from being populated but >> a fix has been pushed for that. >> >> That being said, I also had the hang issue. I did the same as you; >> I did a vagrant ssh from a new terminal >> window and everything worked. Also, after bringing down the virtual >> server and bringing it up again, the problem >> has not recurred. I haven't had the time to figure out why it hung >> in the first place though. >> >> StanD. >> >> >> On 07/08/2011 08:37 AM, Joseph Jones wrote: >> >> I'm having a problem on Max OS X 10.6.8 where vagrant hangs >> setting up the VM right after installing jark. >> It seems to >> just stop doing anything. I initially thought that that meant >> it was completed but opening a new terminal >> window and >> doing vagrant ssh brought me to a VM that had nothing setup. No >> Jark running (in fact no Jark on the path), >> no swank, >> and emacs knew nothing about slime in any way. >> >> I checked out the .emacs.d folder and there was nothing in it >> so obviously whatever step was supposed to put >> something >> there never ran. >> >> Any ideas on what the issue could be? >> >> Thanx, >> joe >> >> >> On Sun, Jun 26, 2011 at 9:50 PM, Justin Lilly < >> jus...@justinlilly.com <mailto:jus...@justinlilly.com**> >> <mailto:jus...@justinlilly.com <mailto:jus...@justinlilly.com* >> *>__>> wrote: >> >> I've put together a simple development environment for >> those looking >> for a stable place to work on clojure code. The idea was >> dual purpose: >> a consistent environment for which to try out multiple code >> bases and >> something that is familiar to me when working on a foreign >> operating >> system. >> >> The included vagrant file will setup an Ubuntu 11.04 >> virtual machine >> with clojure and clojure-contrib 1.2, emacs 24 (with >> emacs-starter-kit >> 2 and all relevant clojure modes), tmux (similar to GNU >> screen), >> Leiningen and Jark. >> >> Special thanks to Phil Hagelberg for his help getting >> things setup. >> >> Please check out the github project hosted by the Seajure >> user group >> at >> https://github.com/Seajure/__**emacs-clojure-vagrant<https://github.com/Seajure/__emacs-clojure-vagrant>< >> https://github.com/Seajure/**emacs-clojure-vagrant<https://github.com/Seajure/emacs-clojure-vagrant> >> > >> >> . Your forks and >> contributions are appreciated. >> >> Thanks, >> -justin >> >> > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscribe@**googlegroups.com<clojure%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/**group/clojure?hl=en<http://groups.google.com/group/clojure?hl=en> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
