Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Should plenary.log provide a way of amending default_config?

Open
#638 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
tooling

Research direction

Start by reading the implementation of plenary.log and locate how default_config is defined and consumed. Determine the public configuration entry point and check any existing logging tests or documentation. Done means users can amend the defaults without replacing log.new, with behavior covered by the relevant tests.

Written by the indexing model from the issue text.

Description

At the moment default_config for plenary is to do this hack:

	{
		"nvim-lua/plenary.nvim",
		config = function()
			local log = require("plenary.log")
			local original_new = log.new

			log.new = function(config, standalone)
				local merged_config = vim.tbl_deep_extend("force", { use_console = false }, config or {})
				return original_new(merged_config, standalone)
			end
		end,
	},

should we expose default_config somehow so people can modify it?

Dominant language
Lua
Stars
3.5k
Forks
340
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.