I'd like to announce a bugfix release for VimClojure.
This release is compatible with Clojure 1.0 and
Clojure-Contrib 919 (in old SVN terms). Other
pre-GTIC contrib versions from Github should also
work. For Clojure(-Contrib) head consider using the
bleeding-edge branch from the repository.
The Ivy configuration will fetch an known-to-work
Clojure(-Contrib) version. For manual compilation,
you have to care for that yourself. A compiled jar
is already included in the distribution in the build
subdirectory.
Changes since v2.1.1:
* Fixed a regression of qualified keywords highlighting
* Fixed a infinite loop if there is no prompt in the Repl buffer
* Made compilation of ng client a bit more comfortable
* Added library configuration for OpenSolaris (thanks to Richard Newman)
* Changed normal invokations to ignore keymappings (reported by James
Reeves)
* Fixed typo in lispwords: defmethod -> defmulti
* Added letfn to lispwords
* Added c.c.def/defnk to lispwords
* Added #_ and #! as comment indicators to syntax highlighting
(currently only the #_ is marked as comment, the following form
is still highlighted normally.)
* Fixed annoying o/O delay bug
* Simplified plugin installation
The release can be found at the usual places:
http://kotka.de/projects/clojure/vimclojure.html
http://bitbucket.org/kotarak/vimclojure
http://www.vim.org/scripts/script.php?script_id=2501
Sincerely
Meikel
Am 14.08.2009 um 19:56 schrieb kjellski:
> And here the great post about how that works in detail:
> http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/
>
> All the kudos to Jonathan Palardy, that changed my work with vim
> and clojure and I hope it will change yours too.
I hope you are aware, that VimClojure can do
all this. You can send expressions to a Clojure
instance, display docstrings, macroexpand
forms.
The screen approach:
+ works also for other languages
- not easily portable to Windows
- only one-way: it can only send commands
but cannot read the result
- it clutters the history of your repl with unrelated
commands
The VimClojure approach:
- works only with Clojure
+ works also well on Windows
+ works two-way: you get features like (halfway)
smart omni-completion, a namespace browser
(which is on the TODO list for quite some time),
go to source location, ...
+ Uses parallel connections: your repl stays clean
Big- uses Clojure itself, so the file needs to be on
the classpath and must be loadable without side
effects (and in particular w/o syntax errors!)
I prefer the VC approach, although the last point
may be of concern to you. For me it works quite
well.
Sincerely
Meikel