Re: running Gorilla

2009-01-21 Thread bOR_
Just for posterity: It took me a while to realize that my fresh vim didn't have a maplocalleader defined. Had to add it to the .vimrc so that chimp (and I guess gorilla as well) would actually have some keybindings associated with it. let maplocalleader = , Gracias! On Dec 19 2008, 8:26 am,

Re: running Gorilla

2009-01-21 Thread Meikel Brandmeyer
Hi, Am 21.01.2009 um 14:06 schrieb bOR_: Just for posterity: It took me a while to realize that my fresh vim didn't have a maplocalleader defined. Had to add it to the .vimrc so that chimp (and I guess gorilla as well) would actually have some keybindings associated with it. let

running Gorilla

2008-12-18 Thread Mark Volkmann
I'm probably doing something wrong, but I haven't been able to get Gorilla to work with Vim. The installation instructions say: 1) Copy the after, doc and plugin directories into your .vim directory. I've done this. My ~/.vim directory now contains afterbin doc ftplugin plugin

Re: running Gorilla

2008-12-18 Thread Randall R Schulz
On Thursday 18 December 2008 11:52, Mark Volkmann wrote: I'm probably doing something wrong, but I haven't been able to get Gorilla to work with Vim. The installation instructions say: ... I've done this, but it doesn't seem to recognize Gorilla shortcuts. Should I be able to open a REPL

Re: running Gorilla

2008-12-18 Thread Meikel Brandmeyer
Hi, Am 18.12.2008 um 20:52 schrieb Mark Volkmann: I've done this, but it doesn't seem to recognize Gorilla shortcuts. Should I be able to open a REPL buffer by entering :sr? The keymappings are only active in Clojure buffers. Try editing a clojure file or set the filetype manually with

Re: running Gorilla

2008-12-18 Thread Randall R Schulz
On Thursday 18 December 2008 12:13, Mark Volkmann wrote: On Thu, Dec 18, 2008 at 2:07 PM, Randall R Schulz rsch...@sonic.net wrote: ... First of all, check whether you Vim has the necessary Ruby support: % vim --version |sed -n -e 1p -e '/ruby/p' ... If you see -ruby then you're

Re: running Gorilla

2008-12-18 Thread Mark Volkmann
On Thu, Dec 18, 2008 at 2:18 PM, Randall R Schulz rsch...@sonic.net wrote: On Thursday 18 December 2008 12:13, Mark Volkmann wrote: On Thu, Dec 18, 2008 at 2:07 PM, Randall R Schulz rsch...@sonic.net wrote: ... First of all, check whether you Vim has the necessary Ruby support: % vim

Re: running Gorilla

2008-12-18 Thread Mark Volkmann
On Thu, Dec 18, 2008 at 4:10 PM, Meikel Brandmeyer m...@kotka.de wrote: Hi, Am 18.12.2008 um 23:06 schrieb Mark Volkmann: Error detected while processing /Users/Mark/.vim/plugin/gorilla.vim: line 558: LoadError: /usr/local/lib/ruby/1.8/i686-darwin9.3.0/socket.bundle:

Re: running Gorilla

2008-12-18 Thread Meikel Brandmeyer
Hi, Am 18.12.2008 um 23:36 schrieb Mark Volkmann: The documentation says LocalLeadersr. I don't know what LocalLeader means. Is that just a colon? The Leader is a key you define yourself. I remapped the \ to , since \ is awkward to type on german keyboards. Leader is for plugins, LocalLeader

Re: running Gorilla

2008-12-18 Thread Mike Perham
I think the point is that the installation documentation is a little lacking right now. Can you create a more thorough install doc which walks us through the setup? I'm an experienced Java developer so I had no problem getting the Gorilla server running but the vim setup is a mystery to me. I

Re: running Gorilla

2008-12-18 Thread Meikel Brandmeyer
Hi, On 19 Dez., 02:47, Mike Perham mper...@gmail.com wrote:  Can you create a more thorough install doc which walks us through the setup? Yes. It seems this is necessary. There is a small screencast available explaining the installation of VimClojure with a minimal set of required options.

Re: running Gorilla

2008-12-18 Thread Axel Schlueter
Hi, On Fri, Dec 19, 2008 at 2:47 AM, Mike Perham mper...@gmail.com wrote: ./after/ftplugin/clojure: total 8 -rw-r--r-- 1 mperham mperham 1698 Dec 18 17:40 gorilla.vim The directory name after is IMHO just meant as a hint like in copy this files AFTER building the gorilla jar but not as

Re: running Gorilla

2008-12-18 Thread Meikel Brandmeyer
Hi, On 19 Dez., 08:04, Axel Schlueter schlu...@gmail.com wrote: The directory name after is IMHO just meant as a hint like in copy this files AFTER building the gorilla jar but not as the name of the final directory. No it is not. The after is there on purpose. It says load this file after