So my problem was the line endings in clojure_emacs.sh were windows- style, not unix.
But now the next problem with my environment is that the output from vagrant up reports that emacs can't open the .emacs.d/init.el file. I suppose it's on this line: emacs --batch -l .emacs.d/init.el -f package-updates And the result is there's no match for M-x slime-connect On Jul 8, 11:47 am, nil <ache...@gmail.com> wrote: > I was using the latest VirtualBox (4.0.10) and it was complaining > about a version mismatch between Guest Additions Version: 4.0.6 and > VirtualBox Version: 4.0.10. So I switched to VirtualBox Version 4.0.6 > instead and the output is below. It no longer complains about the > mismatch. I'm continuing to use PuTTY to ssh. The 4.0.6 machine > behaves the same way as 4.0.10: it suggests that I try sudo apt-get > install emacs. > > emacs-clojure-vagrant>vagrant up > [default] Provisioning enabled with shell... > [default] Importing base box 'natty32'... > [default] Matching MAC address for NAT networking... > [default] Running any VM customizations... > [default] Clearing any previously set forwarded ports... > [default] Forwarding ports... > [default] -- ssh: 22 => 2222 (adapter 1) > [default] Creating shared folders metadata... > [default] Booting VM... > [default] Waiting for VM to boot. This can take a few minutes. > [default] VM booted and ready for use! > [default] Mounting shared folders... > [default] -- v-root: /vagrant > [default] Running provisioner: Vagrant::Provisioners::Shell... > [default] stdin: is not a tty > [default] bash: /tmp/vagrant-shell: /bin/bash^M: bad interpreter: No > such file or directory > The following SSH command responded with a non-zero exit status. > Vagrant assumes that this means the command failed! > > chmod +x /tmp/vagrant-shell > /tmp/vagrant-shell > > The output of the command prior to failing is outputted below: > > [no output] > > emacs-clojure-vagrant> > > On Jul 7, 2:39 pm, Justin Lilly <jus...@justinlilly.com> wrote: > > > > > > > > > emacs24 should be installed. My suggestion would be to delete the vm > > and restart. Perhaps not having putty broke the initial install? If it > > breaks, please send the full output of the console with what is > > broken. > > > -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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
