_      _                     _        _
    | |    | |                   | |      (_)
  __| | ___| |__  _   _  __ _ ___| |_ _ __ _ _ __   __ _
 / _` |/ _ \ '_ \| | | |/ _` / __| __| '__| | '_ \ / _` |
| (_| |  __/ |_) | |_| | (_| \__ \ |_| |  | | | | | (_| |
 \__,_|\___|_.__/ \__,_|\__, |___/\__|_|  |_|_| |_|\__, |
                         __/ |                      __/ |
                        |___/                      |___/

debugstring aims to automate standard debugging operations (e.g., segfaults). It does that by facilitating the ubiquitous printf()-debugging i.e., scatter logging statements around the various code snippets that you want to test.

Presentation at Vim-London

• The form and syntax of the logging statements target the language at hand (e.g., use printf() in C/C++ but puts() in Ruby)
• Support for debugging variable expressions e.g., the values of variables or arbitrary expressions at certain parts of your code
• Support for : Place your cursor over the variable you want to print and press <leader>DS. It will create a debugging string for that variable
• Support for vim-repeat. No need for repeat the same mapping, or rewrite the lengthy expression that you want to monitor, just use the . character

Currently the following languages are supported. First column corresponds to the standard debugging string while the second to the case of debugging for a specific variable.

For a more detailed description of debugstring check doc/debugstring.txt

Use the mappings of your choice to place unique logging directives during debugging times.

nnoremap <your-key-combination> <Plug>DumpDebugString
nnoremap <a-second-key-combination> <Plug>DumpDebugStringExpr
nnoremap <a-third-key-combination> <Plug>DumpDebugStringCexpr

Default mappings are: <Leader>ds, <Leader>dS, <Leader>DS respectively.

An example of using it in a C++ file is given below:

// Debug String
std::cout << "[a.c:4] DEBUGGING STRING ==> " << 0 << std::endl;

// Debug Variable
std::cout << "[a.c:4] a_variable: " << a_variable << std::endl;

• Make sure that filetype plugin is enabled. A line like filetype plugin on in your .vimrc should do the job.

debugstring depends on the following vim plugins:

• vim-repeat [OPTIONAL]

In case you want to contribute on a certain feature/fix, don't hesitate to discuss about it in the Github issues or to implement it and make a PR.

Current plugin is distributed under the same terms as Vim itself. See the LICENSE file

In case you like the plugin, you might as well star it on Github or rate it on vim.org Also feel free to check my other plugins

This mostly comprises a list of stuff I want to keep track of when developing this or other vim plugins

• Use vimdoc to generate documentation from the vim docstring (instead of manually updating the .txt file). See the misc/build_doc for more on how this is done.

• Use vader for unittesting. Use test/run-tests.sh to run them:

  vim -Nu test/vimrc
  :set rtp+=vader.vim/plugin
  :set rtp+=vim-repeat/autoload
  
  :Vader test/*
  

• Method to delete all the debugging strings in current buffer / all "touched" buffers - see far.vim
• Method to print name and contents of a variable
• [ ]Make the counter buffer-specific Nope, we already have the filename & line for file-specific text
• Escape double single quotes vimscript variable printing
• Append to current line if that is empty
• Support repeat.vim
• Use an assertion module - vader
• Use vader.vim for TDD
• Extend vader support for rest of languages
• Use travis for CI
• Bug with changing the filename of the current file
• Make vim-repeat dependency optional
• Turn supported languages into a table - what do we support in which language
• Make vim-repeat dependency optional