From d692659824e7ef7d204735ad7f55196632d68288 Mon Sep 17 00:00:00 2001 From: Preston Hunt Date: Fri, 28 Aug 2026 12:18:52 -0700 Subject: [PATCH] nvim: don't clone lazy.nvim into the current directory setup_nvim ran 'git clone ... lazy.nvim.git --branch=stable' with no destination argument, so the clone landed in $PWD rather than under ~/.local/share/nvim/lazy. Running the script from a checkout of this repo left a stray lazy.nvim/ directory in the working tree. The clone was redundant regardless: init.lua already bootstraps lazy.nvim into stdpath('data')/lazy/lazy.nvim on first launch. Co-Authored-By: Claude Opus 5 (1M context) --- setup | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/setup b/setup index df939ed..1403146 100755 --- a/setup +++ b/setup @@ -378,10 +378,7 @@ setup_nvim() { mkdir -p "$nvimdir" get_prestobuntu_file "init.lua" "$nvimdir/init.lua" install_package fzf - # lazy - local nvimdata="$HOME/.local/share/nvim" - mkdir -p "$nvimdata"/lazy - git clone --filter=blob:none https://github.com/folke/lazy.nvim.git --branch=stable + # lazy.nvim bootstraps itself on first nvim launch; see init.lua } setup_static_ip_address() {