From a1e1910fef19e6e9ee8ee57d184d512efa9b30e1 Mon Sep 17 00:00:00 2001 From: Alan Hamlett Date: Sat, 22 Apr 2017 14:03:27 -0700 Subject: [PATCH] more info about finding errors without debug mode --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index df7b8f4..64d77be 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,8 @@ Run `:WakaTimeDebugEnable` in Vim then run this Terminal command: `tail -f ~/.wakatime.log` Enabling Debug Mode writes Vim Script errors to your Vim Status Bar and tells [wakatime-cli][wakatime-cli] to write verbose logs to `$WAKATIME_HOME/.wakatime.log`. -With Debug Mode enabled, the plugin sends data synchronously so disable it when finished debugging. +Debug mode can make it hard to find the real error because of all the extra logging, so also try disabling Debug Mode while tailing `~/.wakatime.log` and editing files in Vim. +With Debug Mode enabled, the plugin sends data synchronously so disable it when finished debugging with `:WakaTimeDebugDisable`. The [How to Debug Plugins][how to debug] guide shows how to check when coding activity was last received from Vim use the [User Agents API][user agents api]. For more general troubleshooting info, see the [wakatime-cli Troubleshooting Section][wakatime-cli-help].