fork of vim-wakatime that repoints to localhost

Find a file

Alan Hamlett a6f03a085a troubleshooting section in readme		2017-04-22 13:58:32 -07:00
doc	add version 0.1.2	2013-06-25 00:57:15 -07:00
plugin	last_activity_at better name than last_seen_at	2017-04-22 13:40:54 -07:00
.gitignore	v2.0.5	2014-08-07 08:29:01 -07:00
AUTHORS	add authors file and update license	2014-12-21 19:47:29 -06:00
HISTORY.rst	changes for v4.0.15	2017-04-13 23:05:44 -07:00
LICENSE.txt	add authors file and update license	2014-12-21 19:47:29 -06:00
README.md	troubleshooting section in readme	2017-04-22 13:58:32 -07:00

README.md

vim-wakatime

Quantify your coding inside Vim.

Installation

Install Vundle, the Vim plugin manager.
Using Vundle:
echo "Bundle 'wakatime/vim-wakatime'" >> ~/.vimrc && vim +BundleInstall

or using Pathogen:
cd ~/.vim/bundle && git clone git://github.com/wakatime/vim-wakatime.git

Enter your api key, then press enter.
Use Vim and your coding activity will be displayed on your WakaTime dashboard.

Note: WakaTime depends on Python being installed to work correctly.

Screen Shots

Configuring

To use a custom python binary:

let g:wakatime_PythonBinary = '/usr/bin/python'

The default is to use python from your system PATH.

WakaTime plugins share a common config file ~/.wakatime.cfg located in your user home directory with these options available.

Troubleshooting

Run :WakaTimeDebugEnable in Vim to see errors output in your status bar. Enabling Debug Mode also writes verbose logs to $WAKATIME_HOME/.wakatime.log from wakatime-cli. With Debug Mode enabled, the plugin sends data synchronously so disable it when finished debugging.

The How to Debug Plugins guide shows how to check when coding activity was last received from Vim use the User Agents API. For more general troubleshooting info, see the wakatime-cli Troubleshooting Section.

Uninstalling

Remove Bundle 'wakatime/vim-wakatime' from your .vimrc file, then delete your ~/.wakatime.cfg config file.