From 4930200cdc2b00064c773221d4b13aaf88c1d6d8 Mon Sep 17 00:00:00 2001 From: willsALMANJ Date: Fri, 16 May 2014 13:21:37 -0400 Subject: [PATCH] Explain how to get debug output with terminal vim I found this through Valloric/YouCompleteMe#914, but it should probably be in the docs here. --- CONTRIBUTING.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2483a380..00407ca8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,9 +51,11 @@ Here are the things you should do when creating an issue: let g:ycm_server_log_level = 'debug' ``` - Then start gvim/macvim (not console vim) from the console. As you use Vim, - you'll see the `ycmd` debug output stream in the console. Attach that to you - issue. + Then, if possible, start gvim/macvim (not console vim) from the console. + As you use Vim, you'll see the `ycmd` debug output stream in the console. + If you can not use gvim/macvim, run `:YcmDebugInfo` in vim to see what + temporary files (listed under "Server logfiles") the debug output streams + are written to. Attach the debug output stream to your issue. 3. **Create a test case for your issue**. This is critical. Don't talk about how "when I have X in my file" or similar, _create a file with X in it_ and put the contents inside code blocks in your issue description. Try to make this