Skip to content
Browse files

Fix potential butchering of viminfo filename

  • Loading branch information...
1 parent 58e0a99 commit cdd8bc82594cfa69a8c88d264436433882a1416a @tpope committed Jan 8, 2013
Showing with 21 additions and 1 deletion.
  1. +20 −0 README.markdown
  2. +1 −1 plugin/classpath.vim
20 README.markdown
@@ -28,6 +28,26 @@ then simply copy and paste:
Once help tags have been generated, you can view the manual with
`:help classpath`.
+## FAQ
+> Why does it take so long for Vim to startup?
+The short answer is because the JVM is slow.
+The first time you load a Clojure file from any given project, classpath.vim
+sets about trying to determine your class path, leveraging either
+`lein classpath` or `mvn dependency:build-classpath`. This takes a couple of
+seconds or so in the best case scenario, and potentially much longer if it
+decides to hit the network.
+Because the class path is oh-so-expensive to retrieve, classpath.vim caches it
+in `g:CLASSPATH_CACHE`. By default, this disappears when you exit Vim, but
+you can save it across sessions in `.viminfo` with this handy option:
+ set viminfo+=!
+The cache is expired when the timestamp on `project.clj` or `pom.xml` changes.
## Contributing
See the contribution guidelines for
2 plugin/classpath.vim
@@ -7,7 +7,7 @@ endif
let g:loaded_classpath = 1
if &viminfo !~# '!'
- set viminfo+=!
+ set viminfo^=!
augroup classpath

0 comments on commit cdd8bc8

Please sign in to comment.
Something went wrong with that request. Please try again.