Davetron5000 (talk | contribs) mNo edit summary |
Davetron5000 (talk | contribs) mNo edit summary |
||
| Line 12: | Line 12: | ||
If you set <tt>keywordprg</tt> to blank, you can do a <tt>K</tt> on any Java keyword and bring up the javadoc quickly. This has really cut down on the amount of time I spend outside vim while coding. |
If you set <tt>keywordprg</tt> to blank, you can do a <tt>K</tt> on any Java keyword and bring up the javadoc quickly. This has really cut down on the amount of time I spend outside vim while coding. |
||
| − | Go to [http://vimdoclet.sf.net] to download the doclet and see what the output looks like. There is a sample download of javadoc for <tt>java.lang</tt> and <tt>java.util</tt> if you'd like to try it out before running the doclet. |
+ | Go to [http://vimdoclet.sf.net vimdoclet.sf.net] to download the doclet and see what the output looks like. There is a sample download of javadoc for <tt>java.lang</tt> and <tt>java.util</tt> if you'd like to try it out before running the doclet. |
Revision as of 02:03, 27 November 2007
Tip: Vim Doclet
Created: 11/26/2007 Complexity: intermediate Author: User:Name Version: 1.1
By running a doclet on the JDK source code, you can put the resulting vim help files in your help path and read Javadoc from directly within Vim. :help String and :help java.util.List bring up the javadoc for those files, within vim. Everything's hyperlinked and the entire javadoc is present.
If you set keywordprg to blank, you can do a K on any Java keyword and bring up the javadoc quickly. This has really cut down on the amount of time I spend outside vim while coding.
Go to vimdoclet.sf.net to download the doclet and see what the output looks like. There is a sample download of javadoc for java.lang and java.util if you'd like to try it out before running the doclet.
