Skip to content

andrewferrier/debugprint.nvim

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

debugprint.nvim

Test status

Overview

debugprint is a NeoVim plugin that simplifies debugging for those who prefer a low-tech approach. Instead of using a sophisticated debugger like nvim-dap, some people prefer using a 'print'-like statement to trace the output during execution. With debugprint, you can insert these statements, including the values of variables, relevant to the language you're editing.

Features

debugprint is inspired by vim-debugstring; updated for the NeoVim generation. It:

  • Supports 32 filetypes/programming languages out-of-the-box, including Python, JavaScript/TypeScript, Java, C/C++ and more. It can also be extended to support other languages or customize existing ones.

  • Includes reference information in each 'print line' such as file names, line numbers, a counter, and snippets of other lines to make it easier to cross-reference them in output (each of these can be optionally disabled globally or on a per-filetype basis).

  • Can output the value of variables (or in some cases, expressions).

  • Dot-repeats.

  • Can detect a Treesitter variable name under the cursor for some languages, or will prompt with a sensible default. It understands Treesitter embedded languages (e.g. JavaScript-in-HTML).

  • Provides keymappings for normal, insert, visual, and operator-pending modes.

  • Provides commands to delete debugging lines added to the current buffer or comment/uncomment those lines.

  • Can optionally move to the inserted line (or not).

  • Is MIT Licensed.

Demo

211196425-2b371442-54f9-43d7-9187-a29185d43586.mp4

Installation

Requires NeoVim 0.9+.

Example for lazy.nvim:

return {
    "andrewferrier/debugprint.nvim",

    -- opts = { … },

    dependencies = {
        "echasnovski/mini.nvim" -- Needed for :ToggleCommentDebugPrints (not needed for NeoVim 0.10+)
    },
}

(Examples for other package managers here.)

The sections below detail the allowed options that can appear in the opts object. There is also a showcase of example and advanced debugprint configurations here which can be dropped into your configuration files to further enhance your use of debugprint.

Please subscribe to this GitHub issue to be notified of any breaking changes to debugprint.

Keymappings and Commands

By default, the plugin will create some keymappings and commands for use 'out of the box'. There are also some function invocations which are not mapped to any keymappings or commands by default, but could be. This is all shown in the following table.

Mode Default Key / Cmd Purpose Above/Below Line
Normal g?p Plain debug Below
Normal g?P Plain debug Above
Normal g?v Variable debug Below
Normal g?V Variable debug Above
Normal None Variable debug (always prompt for variable) Below
Normal None Variable debug (always prompt for variable) Above
Normal None Delete debug lines in buffer -
Normal None Comment/uncomment debug lines in buffer -
Insert Ctrl-G p Plain debug In-place
Insert Ctrl-G v Variable debug (always prompt for variable) In-place
Visual g?v Variable debug Below
Visual g?V Variable debug Above
Op-pending g?o Variable debug Below
Op-pending g?O Variable debug Above
Command :DeleteDebugPrints Delete debug lines in buffer -
Command :ToggleCommentDebugPrints Comment/uncomment debug lines in buffer -

The keys and commands outlined above can be specifically overridden using the keymaps and commands objects inside the opts object used above during configuration of debugprint. For example, if configuring via lazy.nvim, it might look like this:

return {
    "andrewferrier/debugprint.nvim",
    opts = {
        keymaps = {
            normal = {
                plain_below = "g?p",
                plain_above = "g?P",
                variable_below = "g?v",
                variable_above = "g?V",
                variable_below_alwaysprompt = nil,
                variable_above_alwaysprompt = nil,
                textobj_below = "g?o",
                textobj_above = "g?O",
                toggle_comment_debug_prints = nil,
                delete_debug_prints = nil,
            },
            insert = {
                plain = "<C-G>p",
                variable = "<C-G>v",
            },
            visual = {
                variable_below = "g?v",
                variable_above = "g?V",
            },
        },
        commands = {
            toggle_comment_debug_prints = "ToggleCommentDebugPrints",
            delete_debug_prints = "DeleteDebugPrints",
        },
        -- … Other options
    },
}

You only need to include the keys / commands which you wish to override, others will default as shown above. Setting any key or command to nil will skip it.

The default keymappings are chosen specifically because ordinarily in NeoVim they are used to convert sections to ROT-13, which most folks don't use.

Mapping Deprecation

Warning

Note: as of version 2.0.0, the old mechanism of configuring keymaps/commands which specifically allowed for mapping directly to require('debugprint').debugprint(...) is no longer officially supported or documented. This is primarily because of confusion which arose over how to do this mapping. Existing mappings performed this way are likely to continue to work for some time. You should, however, migrate over to the new method outlined above. If this doesn't give you the flexibility to map how you wish for some reason, please open an issue.

Other Options

debugprint supports the following options in its global opts object:

Option Default Purpose
move_to_debugline false When adding a debug line, moves the cursor to that line
display_location true Include the filename and linenumber of the line being debugged in the debug message
display_counter true Include the increasing integer counter in the debug message. Can also be set to a function to customize, see the showcase) for an example
display_snippet true Include a snippet of the line above/below in the debug message (plain debug lines only) for context
filetypes See (the code) Custom filetypes - see showcase
print_tag DEBUGPRINT The string inserted into each print statement, which can be used to uniquely identify statements inserted by debugprint. If you set this to '' (the empty string), no print tag will be included, but this will disable the ability to delete or comment print statements via debugprint

Known Limitations

  • debugprint does not handle deleting reformatted debug lines where a formatter has split them across multiple lines. If you want to be able to easily delete your debug lines using DeleteDebugPrints or similar, don't format your file between inserting them and running this command. See this issue for discussion on this.

Feature Comparison with Similar Plugins

(This table is quite wide, you may need to scroll horizontally)

Feature debugprint.nvim nvim-chainsaw printer.nvim refactoring.nvim vim-printer logsitter
Auto-generation of debug line, incl. location πŸ‘ ❌ πŸ‘ πŸ‘ ❌ πŸ‘
Print plain debug lines πŸ‘ πŸ‘ ❌ πŸ‘ ❌ ❌
Print variables using current word/heuristic πŸ‘ πŸ‘ ❌ ❌ πŸ‘ ❌
Print variables using treesitter πŸ‘ πŸ‘ ❌ πŸ‘ ❌ ❌
Print variables/expressions using prompts πŸ‘ ❌ ❌ ❌ ❌ ❌
Print variables using motions πŸ‘ ❌ πŸ‘ ❌ ❌ ❌
Add plain or variable debug lines in insert mode πŸ‘ ❌ ❌: ❌ ❌ ❌
Add variable debug lines in visual mode πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘ ❌
Print assertions ❌ πŸ‘ ❌ ❌ ❌ ❌
Print stack traces ❌ πŸ‘ ❌ ❌ ❌ ❌
Add time-tracking logic ❌ πŸ‘ ❌ ❌ ❌ ❌
Add debugging breakpoints ❌ πŸ‘ ❌ ❌ ❌ ❌
Print debug lines above/below current line πŸ‘ ❌ (via global config) ❌ πŸ‘ ❌
Supports dot-repeat πŸ‘ πŸ‘ ❌ ❌ ❌ ❌
Can control whether to move to inserted lines πŸ‘ ❌ ❌ ❌ ❌ ❌
Clean up all debug lines πŸ‘ πŸ‘ ❌ ❌ ❌ ❌
Comment/uncomment all debug lines πŸ‘ ❌ ❌ ❌ ❌ ❌
Can put debugprint text into default register ❌ ❌ πŸ‘ ❌ ❌ ❌
Built-in support for: - - - - - -
Apex (Salesforce) πŸ‘ ❌ ❌ ❌ ❌ ❌
AppleScript πŸ‘ πŸ‘ ❌ ❌ ❌ ❌
bash/sh πŸ‘ πŸ‘ πŸ‘ ❌ πŸ‘ ❌
C πŸ‘ ❌ ❌ ❌ ❌ ❌
C# πŸ‘ ❌ ❌ ❌ ❌ ❌
C++ πŸ‘ ❌ πŸ‘ πŸ‘ πŸ‘ ❌
CMake πŸ‘ ❌ ❌ ❌ ❌ ❌
dart πŸ‘ ❌ ❌ ❌ ❌ ❌
Docker πŸ‘ ❌ ❌ ❌ ❌ ❌
DOS/Windows Batch πŸ‘ ❌ ❌ ❌ ❌ ❌
Elixir πŸ‘ ❌ ❌ ❌ ❌ ❌
fish πŸ‘ ❌ ❌ ❌ ❌ ❌
Fortran πŸ‘ ❌ ❌ ❌ πŸ‘ ❌
Golang πŸ‘ ❌ πŸ‘ πŸ‘ πŸ‘ πŸ‘
Haskell πŸ‘ ❌ ❌ ❌ ❌ ❌
Java πŸ‘ ❌ πŸ‘ πŸ‘ πŸ‘ ❌
Javascript/Typescript πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘
Kotlin πŸ‘ ❌ ❌ ❌ ❌ ❌
lean πŸ‘ ❌ ❌ ❌ ❌ ❌
lua πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘
GNU Make πŸ‘ ❌ ❌ ❌ ❌ ❌
Perl πŸ‘ ❌ ❌ ❌ ❌ ❌
PHP πŸ‘ ❌ ❌ πŸ‘ ❌ ❌
Powershell/ps1 πŸ‘ ❌ ❌ ❌ ❌ ❌
Python πŸ‘ πŸ‘ πŸ‘ πŸ‘ πŸ‘ ❌
R πŸ‘ ❌ ❌ ❌ ❌ ❌
Ruby πŸ‘ πŸ‘ ❌ πŸ‘ ❌ ❌
Rust πŸ‘ πŸ‘ πŸ‘ ❌ πŸ‘ ❌
Swift πŸ‘ ❌ ❌ ❌ ❌ ❌
VimL (vimscript) πŸ‘ ❌ πŸ‘ ❌ πŸ‘ ❌
Zig πŸ‘ ❌ ❌ ❌ ❌ ❌
zsh πŸ‘ ❌ πŸ‘ ❌ πŸ‘ ❌
Add custom filetypes πŸ‘ πŸ‘ πŸ‘ ❌ ❌ πŸ‘
Customizable callback formatter ❌ ❌ πŸ‘ ❌ ❌ ❌
Implemented in Lua Lua Lua Lua VimL Lua

Other similar plugins (less popular or unmaintained):