Hi,

Am 30.01.2010 um 16:17 schrieb Jeff Schwab:

> Hope you don't mind if I add to this thread instead.  By the way, can you 
> suggest a forum for reporting VimClojure bugs and contributing patches?

I didn't want to spam the clojure group with VC specific questions. The 
"default" forum - so to say - for VC support is the VC google group. (See CC). 
(Or me via pm or IRC or so...)

> Suggestion 1:  The default filetype detection that comes with VimClojure uses 
> "setfiletype clojure,".

Already Fixed: 
http://bitbucket.org/kotarak/vimclojure/issue/15/a-leading-messes-up-filetype-recognition

> Suggestion 2:  The default indentation from VimClojure tries to line up the 
> beginning of new lines with unrecognized words on previous lines. If you 
> prefer consistent indentation to this kind of heuristic, make the following 
> change to ~/.vim/indent/clojure.vim:

This is not correct. Lists denote function calls. Here the following heuristics 
apply:

a) fun is in lispwords => add two spaces to indent
b) fun is not in lispwords => align up to the first argument
c) fun is not in lispwords and the there is no argument following on the same 
line => add two spaces to indent

"lispwords" indenting is used for forms like if, with-open, defn, let, ... This 
is the way lispindent of Vim works and and (I think) is a kind of quasi 
standard in the lisp world.

The only edge case might be quoted lists. However I have not a single quoted 
list in my projects. This is handled via vectors in Clojure. So adding 
complexity for non-idiomatic code is not very compelling.

Thank you for your feedback.

Sincerely
Meikel

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to 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
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to