bug: installing canola-collection breaks tracking of unsaved changes #48

Closed
opened 2026-04-20 16:17:45 +00:00 by llakala · 5 comments
llakala commented 2026-04-20 16:17:45 +00:00

Prerequisites

Neovim version

NVIM v0.12.1
Build type: Release
LuaJIT 2.1.1741730670
Run "nvim -V1 -v" for more info

Operating system

NixOS Unstable

Description

I was trying to move a file from one folder to another, with this file layout:

.
├── one/
│   └── "file"
└── two/

I deleted file, exited one, pasted file into two/, and then ran :w. However, I found that even though file had been properly pasted, it was still in its original location.

Doing more testing, I found that this is actually a larger issue. Given this layout:

.
├── subdir/
└── "file"

If we delete file, navigate into subdir, then navigate back out, we no longer have our unwritten changes. It seems that if you ever navigate to a directory of equal or greater length, previous changes are lost.

This only happens with canola-collection installed. When I only install canola, the issue doesn't occur, and all directories are properly tracked.

Steps to reproduce

  1. Install both canola.nvim (on the canola branch, as always) and canola-collection
  2. Create one of the example directory layouts I provided
  3. Observe the issue

Minimal reproduction

I reproduced the issue with this minimal config:

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()
require("lazy").setup({
  spec = {
    {
      "barrettruth/canola.nvim",
      branch = "canola",
      config = function()
        vim.g.canola = {}
      end,
    },
    {
      "barrettruth/canola-collection",
      config = function() end,
    },
  },
})
### Prerequisites - [x] I have searched [existing issues](https://github.com/barrettruth/canola-collection/issues) - [x] I have updated to the latest version ### Neovim version ```text NVIM v0.12.1 Build type: Release LuaJIT 2.1.1741730670 Run "nvim -V1 -v" for more info ``` ### Operating system NixOS Unstable ### Description I was trying to move a file from one folder to another, with this file layout: ``` . ├── one/ │   └── "file" └── two/ ``` I deleted `file`, exited `one`, pasted `file` into `two/`, and then ran `:w`. However, I found that even though `file` had been properly pasted, it was still in its original location. Doing more testing, I found that this is actually a larger issue. Given this layout: ``` . ├── subdir/ └── "file" ``` If we delete `file`, navigate into `subdir`, then navigate back out, we no longer have our unwritten changes. It seems that if you ever navigate to a directory of equal or greater length, previous changes are lost. This only happens with canola-collection installed. When I only install canola, the issue doesn't occur, and all directories are properly tracked. ### Steps to reproduce 1. Install both `canola.nvim` (on the canola branch, as always) and `canola-collection` 2. Create one of the example directory layouts I provided 3. Observe the issue ### Minimal reproduction I reproduced the issue with this minimal config: ```lua vim.env.LAZY_STDPATH = ".repro" load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))() require("lazy").setup({ spec = { { "barrettruth/canola.nvim", branch = "canola", config = function() vim.g.canola = {} end, }, { "barrettruth/canola-collection", config = function() end, }, }, }) ```
barrettruth commented 2026-04-20 22:35:48 +00:00

unable to reproduce after trying multiple times with the minimal reproduction.

please try again on latest canola and canola-collection. a lot of changes just fixed.

for sure feel free to reopen and i'll get back to you asap - i just like to keep things tidy.

also, always feel free to @ me. if i don't respond in a few hours the notification most likely just slipped through the cracks

unable to reproduce after trying multiple times with the minimal reproduction. please try again on latest canola and canola-collection. a lot of changes just fixed. for sure feel free to reopen and i'll get back to you asap - i just like to keep things tidy. also, always feel free to @ me. if i don't respond in a few hours the notification most likely just slipped through the cracks
llakala commented 2026-04-21 04:38:53 +00:00

Yep, I can't recreate either anymore - must've fixed it by accident.

Yep, I can't recreate either anymore - must've fixed it by accident.
barrettruth commented 2026-04-27 00:57:27 +00:00

@llakala hv u had any problems, i plan on releasing tmrw

@llakala hv u had any problems, i plan on releasing tmrw
llakala commented 2026-04-27 01:07:58 +00:00

Nope, things have been working well. I'll update to the latest commit now to see if I notice anything.

Nope, things have been working well. I'll update to the latest commit now to see if I notice anything.
barrettruth commented 2026-04-27 01:40:31 +00:00

orz (i hadn't really made any changes - was just wondering

orz (i hadn't really made any changes - was just wondering
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/canola-collection#48
No description provided.