wbthomason/packer.nvim

Disabled plugins get picked up by PackerClean

Open

#56 opened on Sep 26, 2020

View on GitHub
 (12 comments) (2 reactions) (1 assignee)Lua (8,097 stars) (264 forks)batch import
documentationenhancementhelp wantedoverdue_for_fixquestion

Description

I sometimes want to disable plugins along with their associated configuration while still keeping them installed and up to date. I assumed that was the goal of the disable option but the :PackerClean command asks me if I want to remove plugins that are disabled. Am I misunderstanding the purpose of disable?

Contributor guide

Tech stack
lua
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Neovim plugin management basicsLua scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue reports that disabled plugins are still being considered by PackerClean. Investigate the code in packer.lua (likely the main plugin file) to see how PackerClean iterates over plugins and whether it filters out those marked as disabled. The discussion suggests that the disable option should prevent the plugin from being considered in operations like clean. Look for any recent commits or PRs related to this behavior; there may be a simple conditional missing.