From f0ff86d79fac7888d93003c0c8cde1e7deadc636 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alejandro=20Gonz=C3=A1lez?= Date: Mon, 10 Aug 2026 22:15:50 +0200 Subject: [PATCH 1/2] docs: replace unused `dotfiles_installCommand` config option with `dotfiles_install_command` Ever since documentation and devcontainer CLI launching code was reworked on https://github.com/erichlf/devcontainer-cli.nvim/commit/43ae866d8e7adfe0b79b5d92f93a0edc5e9a2327#diff-1b38a8285e8e71b146aa9a90a37fa3edf2d5d7ec1ccb76c21c0427b245c9c434R156, `devcontainer-cli.nvim` reads the install command value from the `dotfiles_install_command` config variable, instead of the `dotfiles_installCommand` variable documented everywhere else. This bug usually does not affect functionality because the devcontainer CLI [falls back to a list of well-known install commands](https://github.com/devcontainers/cli/blob/58be9705761d276b5076525438bbe73642f521d5/src/spec-common/dotfiles.ts#L11-L20) when an install command is not set explicitly. However, as soon as an attempt to use `dotfiles_installCommand` to set a non-conventional install command is made, the bug obviously surfaces after paying attention to the devcontainer CLI output. This change fixes the mismatch by updating the documentation to match the variable actually used in the code, and dropping the useless `dotfiles_installCommand` default from the `default_config` table, with a comment noting the devcontainer CLI fallback behavior the plugin was relying on. I have decided against modifying the code to match the documentation instead because I recognize that maybe I'm not the first person to notice this mismatch, and as such it's possible that there is some plugin configuration out there depending on the variable name that already works. --- README.md | 6 +++--- lua/devcontainer-cli/config.lua | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f3555c1..88ffbd2 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,7 @@ Using **lazy.nvim**: dotfiles_repository = "https://github.com/erichlf/dotfiles.git", dotfiles_branch = "devcontainer-cli", dotfiles_targetPath = "~/dotfiles", - dotfiles_installCommand = "install.sh", + dotfiles_install_command = "install.sh", shell = "bash", nvim_binary = "nvim", log_level = "debug", @@ -128,7 +128,7 @@ Call `require("devcontainer-cli").setup({ ... })` with any of the following opti dotfiles_repository = "https://github.com/erichlf/dotfiles.git", dotfiles_branch = "devcontainer-cli", dotfiles_targetPath = "~/dotfiles", - dotfiles_installCommand = "install.sh", + dotfiles_install_command = "install.sh", -- Shell used when executing commands shell = "bash", @@ -222,7 +222,7 @@ No. You can either keep Neovim on the host and use `:DevcontainerExec`, or conne This plugin focuses on using the official Dev Container CLI and avoids imposing opinions. Similar projects include `esensar/nvim-dev-container` and `arnaupv/nvim-devcontainer-cli`; if you prefer a different model (e.g., host Neovim + remote LSP servers), compare approaches and pick what suits you. **Where should I keep my dotfiles?** -Point `dotfiles_repository` to any repo. The plugin will clone that repo into the container and run your setup script (`dotfiles_installCommand`). +Point `dotfiles_repository` to any repo. The plugin will clone that repo into the container and run your setup script (`dotfiles_install_command`). --- diff --git a/lua/devcontainer-cli/config.lua b/lua/devcontainer-cli/config.lua index 8ce8f8f..505103a 100644 --- a/lua/devcontainer-cli/config.lua +++ b/lua/devcontainer-cli/config.lua @@ -39,7 +39,7 @@ local default_config = { dotfiles_targetPath = "~/dotfiles", -- command that's executed for installed the dependencies from the -- setup_environment_repo - dotfiles_installCommand = "install.sh", + -- dotfiles_install_command = "install.sh", -- Let the devcontainer CLI choose -- The number of columns to wrap text at terminal_columns = 80, -- The particular binary to use for connecting to in the devcontainer From dba03685a222d90b22517b8b09d3bd22f3d43022 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alejandro=20Gonz=C3=A1lez?= Date: Mon, 10 Aug 2026 22:53:13 +0200 Subject: [PATCH 2/2] docs(README): tweak default `dotfiles_install_command` value description --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 88ffbd2..c782831 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ Call `require("devcontainer-cli").setup({ ... })` with any of the following opti dotfiles_repository = "https://github.com/erichlf/dotfiles.git", dotfiles_branch = "devcontainer-cli", dotfiles_targetPath = "~/dotfiles", - dotfiles_install_command = "install.sh", + dotfiles_install_command = nil, -- Let the Dev Container CLI pick a default -- Shell used when executing commands shell = "bash", @@ -222,7 +222,7 @@ No. You can either keep Neovim on the host and use `:DevcontainerExec`, or conne This plugin focuses on using the official Dev Container CLI and avoids imposing opinions. Similar projects include `esensar/nvim-dev-container` and `arnaupv/nvim-devcontainer-cli`; if you prefer a different model (e.g., host Neovim + remote LSP servers), compare approaches and pick what suits you. **Where should I keep my dotfiles?** -Point `dotfiles_repository` to any repo. The plugin will clone that repo into the container and run your setup script (`dotfiles_install_command`). +Point `dotfiles_repository` to any repo. The plugin will clone that repo into the container and run the configured setup script (`dotfiles_install_command`). ---