[ANN] emacs-clojure-vagrant: a sane development virtual environment
Justin Lilly
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 . Your forks and
contributions are appreciated.
Thanks,
-justin
Brett Morgan
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Phil Hagelberg
> I just tried out your vagrant script, and it appears to be dying on an
> unmet dependency:
>
> [default] --2011-06-27 06:33:42--
> https://github.com/downloads/icylisper/jark/jark-0.3
> [default] 207.97.227.239
> [default]
> [default] connected.
> [default] 404 Not Found
> [default] 2011-06-27 06:33:44 ERROR 404: Not Found.
>
> Any suggestions for working around this?
I just opened an issue for this last night. For the time being it may be
best to just comment out the jark section of the script until it's fixed.
https://github.com/icylisper/jark/issues/51
-Phil
Brett Morgan
--
isaac praveen
Sorry about the missing link. Github upload had some issues with
Chrome and hence took a while for me to update the latest jark-0.3
binary. It is up now:
https://github.com/downloads/icylisper/jark/jark-0.3
--
isaac
http://icylisper.in
nil
something like cygwin? Thanks in advance!
[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]
Justin Lilly
this is squarely an issue with the vagrant installation. I would
suggest reading
http://vagrantup.com/docs/getting-started/setup/windows.html
As a starting point. Vagrant related channels should be able to help
you further (but please communicate your solution back to the group!).
Thanks,
-justin
Sunil S Nandihalli
Sunil.
nil
mentioned) helps. PuTTY successfully gives me a vagrant@natty session
*but* "vagrant ssh" doesn't behave any differently -- so I can't tell
if this is fine or if I'm missing something.
Also, if I type emacs at the prompt, I get the following... I thought
emacs 24 was in the VM, no?
vagrant@natty:~$ emacs
The program 'emacs' can be found in the following packages:
* emacs23
* emacs23-nox
* e3
* emacs-snapshot
* emacs-snapshot-nox
* emacs23-lucid
* jove
Try: sudo apt-get install <selected package>
vagrant@natty:~$
Justin Lilly
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
Joseph Jones
nil
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] 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]
Stan Dyck
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>> 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 . 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 clo...@googlegroups.com <mailto:clo...@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+u...@googlegroups.com <mailto:clojure%2Bunsu...@googlegroups.com>
Joseph Jones
To post to this group, send email to clo...@googlegroups.com <mailto: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
For more options, visit this group at
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 clo...@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
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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
Joseph Jones
Stan Dyck
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 <darkdes...@gmail.com <mailto:darkdes...@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.
>
>
> at https://github.com/Seajure/__emacs-clojure-vagrant <https://github.com/Seajure/emacs-clojure-vagrant>
Phil Hagelberg
Running the script will probably need Audi fwiw.
-Phil
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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
nil
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
Joseph Jones
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.
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.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com