nvim-chainsaw 🪚

Quick and feature-rich insertion of various kinds of log statements.

demo.mp4

Table of Contents

• Features
• Installation
• Built-in language support
• Usage
  • List of commands
  • Smart variable detection
  • Smart insertion locations
• Configuration
  • Basic configuration
  • Customize log statements
  • The global pretty-logging function Chainsaw()
  • Make the formatter ignore the log statements
  • Status line
• Comparison with similar plugins
• About the developer

Features

• Quick insertion of log statements for the variable under the cursor (normal mode) or the selection (visual mode).
• Smart detection of the variable under the cursor and the correct insertion location of the log statement via Treesitter.
• Commands for a dozen different log statement types, including assert statements, stack traces, or acoustic logging. All commands are dot-repeatable.
• Built-in support for ~20 common languages, with dedicated support for nvim-lua. Easy configuration for additional languages.
• Helper commands to remove all log statements created by nvim-chainsaw or to clear the console.
• Flexible templating options for customizing log statements, including support for multi-line templates.
• Statusline component to display the count of log statements in the current buffer. Visual indication of log statements via line-highlights, signcolumn, or scrollbar (when using satellite.nvim).
• Auto-install a pre-commit hook that prevents committing files with the log statements created by nvim-chainsaw (opt-in).

Installation

Requirements

• nvim 0.10 or higher.
• Recommended: Treesitter parser for the respective languages to enable smart variable identification and smart insertion locations.

-- lazy.nvim
{ 
	"chrisgrieser/nvim-chainsaw", 
	event = "VeryLazy",
	opts = {} -- required even if left empty
},

-- packer
use { 
	"chrisgrieser/nvim-chainsaw"
	config = function () 
		require("chainsaw").setup()
	end,
}

Built-in language support

• JavaScript/TypeScript (and supersets)
• Python
• Lua (with special considerations for nvim-lua¹)
• bash & zsh
• AppleScript
• Ruby
• Rust
• CSS² (and supersets)
• Go³

Not every language supports every type of log statement. For the concrete statements used, see log-statements-data.lua.

Usage

List of commands

The plugin offers various types of log statements. Bind keymaps for the ones you want to use.

All operations are dot-repeatable.

-- log the name & value of the variable under the cursor
require("chainsaw").variableLog()

-- like variableLog, but with syntax specific to inspect an object, for example
-- `console.log(JSON.stringify(foobar))` in javascript
require("chainsaw").objectLog()

-- inspect the type of the variable under cursor, such as `typeof foo` in js
require("chainsaw").typeLog()

-- assertion statement for variable under cursor
require("chainsaw").assertLog()

-- Minimal log statement, with an emoji for differentiation. Intended for
-- control flow inspection, that is to quickly glance whether a condition was
-- triggered or not.
require("chainsaw").emojiLog()

-- Sound-playing statement for audible debugging.
-- Depending on the type of log statement, it is either a terminal bell
-- (requiring the terminal) or a system sound.
-- Inspired by https://news.ycombinator.com/item?id=41519046
require("chainsaw").sound()

-- create log statement, and position the cursor to enter a message
require("chainsaw").messageLog()

-- 1st call: start measuring the time
-- 2nd call: log the time duration since the 1st statement
require("chainsaw").timeLog()

-- debug statements like `debugger` in javascript or `breakpoint()` in python
require("chainsaw").debugLog()

-- prints the stacktrace of the current call
require("chainsaw").stacktraceLog()

-- clearing statement, such as `console.clear()`
require("chainsaw").clearLog()

---------------------------------------------------

-- remove all log statements created by nvim-chainsaw
require("chainsaw").removeLogs()

These features can also be accessed with the user command :Chainsaw. Each option corresponds to the commands above. For example, :Chainsaw variableLog is same as :lua require("chainsaw").variableLog().

When using lua functions, variableLog, objectLog, typeLog, and assertLog can also be used in visual mode to use the visual selection instead of the word under the cursor.

Smart variable detection

When the variable under the cursor is an object with fields, chainsaw attempts to automatically select the correct field. (Note that this feature requires the Treesitter parser of the respective language.)

myVariable.myF[i]eld = "foobar"
-- prints: myVariable.myField

myVa[r]iable.myField = "foobar"
-- prints: myVariable

Filetypes currently supporting this feature:

• Lua (and nvim_lua)
• Python
• JavaScript (and supersets)

PRs adding support for more languages are welcome. See smart-var-detect.lua.

Smart insertion locations

chainsaw by default inserts the log statement below the cursor. The insertion location is automatically adapted if doing would result in invalid code. (Note that this feature requires the Treesitter parser of the respective language.)

-- [] marks the cursor position

-- default case: will insert the log statement below the cursor
local f[o]obar = 1

-- multi-line assignments: will insert log statement below the `}` line
local f[o]o = {
	bar = 1
}

-- returns: will insert log statement above the `return` line
local function foobar()
	return f[o]o
end

Filetypes currently supporting this feature:

• Lua (and nvim_lua)
• JavaScript (and supersets)

PRs adding support for more languages are welcome. See smart-insert-location.lua.

Configuration

The setup() call is required.

Basic configuration

-- default settings
require("chainsaw").setup {
	-- The marker should be a unique string, since signs and highlgiths are based
	-- on it and since `.removeLogs()` will remove any line with it. Thus, emojis
	-- or unique strings like "[Chainsaw]" are recommended.
	marker = "🪚",

	-- Appearance of lines with the marker
	visuals = {
		sign = "󰹈",
		statuslineIcon = "󰹈",
		notificationIcon = "󰹈",
		signHlgroup = "DiagnosticSignInfo",
		lineHlgroup = false,

		nvimSatelliteIntegration = {
			enabled = true,
			hlgroup = "DiagnosticSignInfo",
			icon = "▪",
			leftOfScrollbar = false,
			priority = 40, -- compared to other handlers (diagnostics are 50)
		},
	},

	-- Auto-install a pre-commit hook that prevents commits containing the marker
	-- string. Will not be installed if there is already another pre-commit-hook.
	preCommitHook = {
		enabled = false,
		notifyOnInstall = true,
		hookPath = ".chainsaw", -- relative to git root

		-- Will insert the marker as `%s`. (Pre-commit hooks requires a shebang.
		-- The hook should exit non-zero when marker is found, to block the commit.)
		hookContent = [[#!/bin/sh
			git grep --fixed-strings --line-number "%s" . || exit 0
			echo
			echo "nvim-chainsaw marker found. Aborting commit."
			exit 1
		]],

		-- If you track your nvim-config via git, and use a custom marker, you
		-- should add it to this list, since your config will then always include
		-- a marker, thus always falsely triggering the pre-commit hook.
		notInNvimConfigDir = true,

		-- List of directories where the hook should not be installed if they are
		-- the git root. Supports globs and `~`. Must *fully* match the directory.
		dontInstallInDirs = {
			-- "~/special-project"
			-- "~/repos/**",
		},
	},

	-- configuration for specific logtypes
	logTypes = {
		emojiLog = {
			emojis = { "🔵", "🟩", "⭐", "⭕", "💜", "🔲" },
		},
	},

	-----------------------------------------------------------------------------
	-- see https://github.com/chrisgrieser/nvim-chainsaw/blob/main/lua/chainsaw/config/log-statements-data.lua
	logStatements = require("chainsaw.config.log-statements-data").logStatements,
	supersets = require("chainsaw.config.log-statements-data").supersets,
}

Customize log statements

New log statements can be added, and existing log statements can be modified under the config logStatements. See log-statements-data.lua for the built-in log statements as reference. PRs adding log statements for more languages are welcome.

There are various placeholders that are dynamically replaced:

• {{marker}} inserts the value from config.marker. Each log statement should have one, so that the line can be removed via .removeLogs().
• {{var}}: variable as described further above.
• {{time}}: timestamp formatted as HH:MM:SS (for millisecond-precision, use .timeLog() instead)
• {{filename}}: basename of the current file
• {{lnum}}: current line number
• .emojiLog() only: {{emoji}} inserts the emoji
• .timeLog() only: {{index}} inserts a running index. (Needed to differentiate between variables when using timeLog multiple times).

require("chainsaw").setup ({
	logStatements = {
		variableLog = {
			javascript = 'console.log("{{marker}} {{var}}:", {{var}});',
			otherFiletype = … -- <-- add the statement for your filetype here
		},
		-- the same way for the other log statement operations
	},
})

Note

The strings may not include line breaks. If you want to use multi-line log statements, use a list of strings instead, each string representing one line.

The global pretty-logging function Chainsaw()

The plugin provides a globally accessible function Chainsaw(), specifically designed for debugging nvim_lua. Given a variable, it pretty-prints the variable, its name, and the location of the log statement call, all in a much more concise manner.

Requirements: A notification plugin like nvim-notify or snacks.nvim. Syntax highlighting inside the notification requires snacks.nvim.

Setup: You can use it by setting a custom log statement like this:

require("chainsaw").setup {
	logStatements = {
		variableLog = {
			nvim_lua = "Chainsaw({{var}}) -- {{marker}}",
		},
	},
}

Tip

To use Chainsaw() during or shortly after startup, you may not lazy-load nvim-chainsaw. Using lazy.nvim, set lazy = false and if needed priority = 200 to ensure the plugin loads before other start-plugins.

The lua_ls diagnostic undefined-global for Chainsaw can be disabled with one of the following methods:

Options

-- Option 1: nvim-lspconfig
require("lspconfig").lua_ls.setup {
	settings = {
		Lua = {
			diagnostics = {
				globals = { "Chainsaw", "vim" },
			},
		},
	},
}

// Option 2: .luarc.json
{
	"diagnostics": {
		"globals": ["Chainsaw", "vim"],
	},
}

-- Option 3: lazydev.nvim
opts = {
	library = {
		{ path = "nvim-chainsaw", words = { "Chainsaw" } },
	},
},

Make the formatter ignore the log statements

A common problem is that formatters like prettier split up the log statements into multiple lines, making them hard to read and breaking .removeLogs(), which relies on each line containing the marker emoji.

The simplest method to deal with this is to customize the log statement in your configuration to include an ignore-comment: /* prettier-ignore */

• The log statements do not accept lines, but you can use a list of strings, where each element is one line.
• Add the marker to the added line as well, so it is included in the removal by .removeLogs().

require("chainsaw").setup {
	logStatements = {
		variableLog = {
			javascript = {
				"/* prettier-ignore */ // {{marker}}",
				'console.log("{{marker}} {{var}}:", {{var}});',
			},
		},
	},
}

Status line

This function returns number of log statements by nvim-chainsaw in the current buffer, for use in your status line.

require("chainsaw.visuals.statusline").countInBuffer()

Comparison with similar plugins

	nvim-chainsaw	debugprint.nvim	timber.nvim
log types	variables, objects, asserts, types, sound, stacktraces, emoji, messages, debugger, time, clear-console	variables	variables, objects, time
builtin language support	~20	~35	~15
inheritance of log statements from superset langs	✅	❌	❌
delete all log statements	✅	✅	✅
comment all log statements	❌	✅	✅
protection to accidentally commit log statements	via auto-installed pre-commit hook (opt-in)	❌	❌
log statement customization	line numbers, filenames, time, multi-line statements	line numbers+filename (location), nearby line snippet, unique counter	line numbers, insertation location
insertation location	below, treesitter-based adjustments for some languages	below, above	below, above, surround, operator, treesitter-based adjustments
variable detection	word under cursor, visual selection, treesitter-based selection	word under cursor, operator, visual selection, treesitter-based selection	word under cursor, visual selection, treesitter-based selection
dot-repeatability	✅	✅	✅
visual emphasis of log statements	signcolumn, line-highlight, statusline, scrollbar	❌	flash on inserting statement
extra features for nvim_lua	separate configuration, availability of global debugging function	❌	❌
log file watcher	❌	❌	✅
maintanability / efficiency	~1000 LoC	~1600 LoC	~4500 LoC (excluding tests)

About the developer

In my day job, I am a sociologist studying the social mechanisms underlying the digital economy. For my PhD project, I investigate the governance of the app economy and how software ecosystems manage the tension between innovation and compatibility. If you are interested in this subject, feel free to get in touch.

I also occasionally blog about vim: Nano Tips for Vim

• Website
• Mastodon
• ResearchGate
• LinkedIn

Footnotes

1. variableLog for nvim_lua uses a log statement that inspects objects and is designed to work with various notification plugins like nvim-notify, snacks.nvim, or noice.nvim. If using snacks.nvim, lua syntax highlighting is added as well. ↩

2. Uses statements such as outline: 2px solid red !important; that are the somewhat similar logging. ↩

3. The packages fmt and time need to be imported manually. ↩