[ANN] vimclojure 2.3.4 released

37 views
Skip to first unread message

Meikel Brandmeyer

unread,
Aug 8, 2012, 5:17:00 PM8/8/12
to vimcl...@googlegroups.com, clojur...@googlegroups.com
Hi,

I just release vimclojure 2.3.4. This is a bugfix release.

* Fixed some typos in the documentation (thanks to Ambrose Bonnaire-Sergeant)
* Mark temporary vimclojure buffers with vimclojure filetype (patch by Krisa Jenkins)
* Reworked window handling of vimclojure temporary buffers
* Fixed indentation of functions with multibyte names (patch by Sung Pae)

Kind regards
Meikel

signature.asc

Sung Pae

unread,
Aug 11, 2012, 1:32:34 AM8/11/12
to vimcl...@googlegroups.com
On 8 Aug 2012, at 4:17 PM, Meikel Brandmeyer wrote:

> I just release vimclojure 2.3.4. This is a bugfix release.


Hi Meikel,

Will you be pushing this release to your bitbucket repository?

Meikel Brandmeyer

unread,
Aug 11, 2012, 3:36:56 AM8/11/12
to vimcl...@googlegroups.com
Argh. Yes. As usual. But I will only return at home tomorrow evening. So you'll have to wait for another day.

Meikel

Durch MOTOBLUR™ verbunden


-----Ursprüngliche Nachricht-----
--
You received this message because you are subscribed to the Google Groups "vimclojure" group.
To post to this group, send email to vimcl...@googlegroups.com.
To unsubscribe from this group, send email to vimclojure+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/vimclojure?hl=en.

Wolodja Wentland

unread,
Aug 15, 2012, 11:33:40 AM8/15/12
to vimcl...@googlegroups.com, clojur...@googlegroups.com
On Wed, Aug 08, 2012 at 23:17 +0200, Meikel Brandmeyer wrote:

> I just release vimclojure 2.3.4. This is a bugfix release.

... and a bugcause one too! :)

I had a problem with the new resultBuffer handling after upgrading to 2.3.4.
Every time I tried to compile with \ef I was shown a buffer with the following
content:

--- snip ---
; Use \p to close this buffer!

Vim(call):E121: Undefined variable: resultBuffer
--- snip ---

I fixed the issue with the supplied patch and it is working so far, but I have
no idea if my changes are the best way to handle this problem. (essentially
call local "buf" instead of the undefined resultBuffer)
--
Wolodja <bab...@gmail.com>

4096R/CAF14EFC
081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
resultBuffer.patch
signature.asc
Reply all
Reply to author
Forward
0 new messages