bug: installing canola-collection breaks tracking of unsaved changes #48
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/canola-collection#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Prerequisites
Neovim version
Operating system
NixOS Unstable
Description
I was trying to move a file from one folder to another, with this file layout:
I deleted
file, exitedone, pastedfileintotwo/, and then ran:w. However, I found that even thoughfilehad 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:
If we delete
file, navigate intosubdir, 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
canola.nvim(on the canola branch, as always) andcanola-collectionMinimal reproduction
I reproduced the issue with this minimal config:
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
Yep, I can't recreate either anymore - must've fixed it by accident.
@llakala hv u had any problems, i plan on releasing tmrw
Nope, things have been working well. I'll update to the latest commit now to see if I notice anything.
orz (i hadn't really made any changes - was just wondering