Update neovim-client readme

Author: jebberjeb

README.md

@@ -1,41 +1,37 @@
 # neovim-client
 
-A Neovim client library for creating plugins written in Clojure, using
-msgpack-rpc + a sample plugin.
-
-Note that this is pretty much reference implementation quality at best 
--- nothing Clojars worthy as yet. The ultimate goal here is the easiest,
-most effective possible Vim plugins written with Clojure.
+A Neovim client library for creating plugins written in Clojure.
 
 ## Dependencies
 
 ### Neovim
 
-I've been building from [master](https://github.com/neovim/neovim).
-
-### Leiningen
-
-At least version 2.5.2 of [Leiningen](https://github.com/technomancy/leiningen/).
+I've been building from [master](https://github.com/neovim/neovim). Currently,
+I'm using `NVIM v0.1.2-220-g3b94756`.
 
 ### Java
 
-You've probably already got this if you're using Clojure. If not, whatever JVM your package manager installs should work.
+You've probably already got this if you're using Clojure. Version 1.6 or later is required.
 
 ## Usage
 
 ### Repl
 
-Launch Neovim, explicitly setting the NVIM_LISTEN_ADDRESS
+Launch Neovim, explicitly setting the `NVIM_LISTEN_ADDRESS`
 
-    NVIM_LISTEN_ADDRESS=127.0.0.1:7777 nvim
+```
+NVIM_LISTEN_ADDRESS=127.0.0.1:7777 nvim
+```
 
-From the cloned repository's directory:
+From repository:
 
-    lein repl
-    neovim-client.nvim=> (connect! "localhost" 7777)
-    ...
-    neovim-client.nvim=> (run-command! ":echo 'Hello Neovim!'")
-    ...
+```
+$> lein repl
+neovim-client.nvim=> (connect! "localhost" 7777)
+...
+neovim-client.nvim=> (run-command! ":echo 'Hello Neovim!'")
+...
+```
 
 [![Repling Neovim](http://img.youtube.com/vi/g-9DdVwbSTo/0.jpg)](https://www.youtube.com/watch?v=g-9DdVwbSTo)
 
@@ -45,54 +41,42 @@ Several sample plugins -- consumers of neovim-client -- are included.
 
 #### Installation
 
-For now (no Clojars yet), we need neovim-client installed locally, so from
-the cloned repository's directory:
-
-    lein install
-
-Install sample-plugin-whatever however you normally do it. For example, using
-Vundle you'd add the following line to your .vimrc:
-
-    Plugin 'file:///path/to/neovim-client', {'rtp': 'sample-plugin-whatever/'}
-
-Finally, to invoke the plugin launch nvim and run:
-
-    :VundleInstall
+While these plugins can be installed locally, the easiest thing to do is to
+run them from the repl, as described above. Simply use `lein repl` from the
+plugin project's root directory.
 
 #### Simple Plugin
 
-    :call RunSamplePluginSimple()
+```
+:call RunSamplePluginSimple()
+```
 
 #### Count Plugin
 
 This plugin stays running, and maintains state. Additionally, it shows how
 plugins are actually servers, which Neovim can make requests to via
 rpcrequest().
 
-    :echo SamplePluginCount() ;; repeat!
+```
+:echo SamplePluginCount()
+```
+
+#### Socket Repl Plugin
+
+TODO
 
 ## Future
 
 ### Tighter Integration with Neovim
 
-Neovim's strategy for [remote plugins](http://neovim.io/doc/user/remote_plugin.html#remote-plugin) says that it's ok to create a remote plugins as "arbitrary programs that communicate directly with the high-level Nvim API and are called via [msgpack-rpc]". That's exactly what the included sample-plugin does (utilizing neovim-client). 
+Neovim's strategy for [remote plugins](http://neovim.io/doc/user/remote_plugin.html#remote-plugin) says that it's ok to create a remote plugins as "arbitrary programs that communicate directly with the high-level Nvim API and are called via [msgpack-rpc]". That's exactly what the included sample-plugin does (utilizing neovim-client).
 
 However, it goes on to outline a better approach, utilizing a "plugin host". While neovim-client could potentially fill that role, considerably more work is needed.
 
-The bottom line is this works, and possibly using ClojureScript w/ node.js, it could be fast too!
-
-### Leiningen Template
-
-A Leiningen template for a Neovim plugin, using neovim-client, and including
-the necessary VimScript hooks.
-
-### Stop Using lein run
-
-Using a VimScript hook, Neovim calls `lein run` to launch the plugin. This isn't
-really Leiningen's job, but it's convenient for a few reasons:
+### Performance
 
-* Single script to distribute, rather than clojure.jar, plugin jar, etc.
-* Makes it easy for a plugin user to modify it - just edit .clj source.
+Individual plugins can be distributed as jars using AOT compilation, as is the
+case for the socket repl plugin. Additionally, porting this client library to Clojurescript would facilitate a fast startup time, via Node.
 
 ## License