Meikel Brandmeyer wrote:
Please send me your suggestions for FAQ and other tips via private email or add a ticket
in the bb tracker for the "documentation" component.
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?
Suggestion 1: The default filetype detection that comes with VimClojure
uses "setfiletype clojure," which is fine most of the time, but fails
when Vim has already identified the file type as something else; for
example, if your first line is "#!/usr/bin/env clj," Vim will already
have set ft=conf. To make VimClojure override those settings, change
~/.vim/ftdetect/clojure.vim:
1c1
< au BufNewFile,BufRead *.clj setfiletype clojure
---
> au BufNewFile,BufRead *.clj set filetype=clojure
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:
162,172c162
< if &lispwords =~ '\<' . w . '\>'
< return paren[1] + &shiftwidth - 1
< endif
<
< normal! w
< if paren[0] < line(".")
< return paren[1] + &shiftwidth - 1
< endif
<
< normal! ge
< return col(".") + 1
---
> return paren[1] + &shiftwidth - 1
--
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
