On Windows, modifying scores via ```zoxide edit``` results in a double slashed duplicate of the path

[ciwolsey]

Runnining zoxide edit on Windows and then attempting to increment or decrement a score causes the path to be added to the database again but with double slashes.

[ciwolsey]

Maybe this could be related to #538?

[WitchGod]

Confirming this is also happeing to me. Same as #538. Originally did it in Powershell 7/Core then got to replicate it in 5.1. Looks like a Windows bug. With the database serialized, I don't think it's an easy edit via source editor as well.

[princemaple]

Happening to me as well. Windows11, nushell.

[Bocom]

Happening to me as well, both this and #538, on Windows 11 and PowerShell 7.

[ArcusCerebellumus]

+1

[YDX-2147483647]

FYI, Swarnim Arun is drafting #569, which may fix all problems by distinguish Path/PathBuf from str/String. (And I suggest we stop +1 again and use the reaction emoji buttons 👍/🚀/…)

[hme3]

Any solution or workaround?

[LoicRiegel]

Just tested on my side with zoxide 0.9.7 with both powershell 5.1 and nushell 0.102.0 on Windows 11 and it works: zoxide edit -> increment / decrement some paths -> I see no duplicate being added...
The issue was created a long time ago now, I guess it's been fixed in the meantime?

[MrDwarf7]

This seems to have been resolved, I no longer experience this either. (Was previously using Windows Terminal, now wezterm, $v tables below.

 ❯ echo $PSVersionTable && Write-Host && wezterm -V && zoxide -V # -->

Name                           Value
----                           -----
PSVersion                      7.6.0-preview.2
PSEdition                      Core
GitCommitId                    7.6.0-preview.2
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

wezterm 20240203-110809-5046fc22
zoxide 0.9.7

This can likely be closed unless others are still experiencing this.

Edit:
Add zoxide version output lol

[YDX-2147483647]

I also confirm that this issue is resolved.

#539 (comment) was posted on 2024-02-16, but https://github.com/ajeetdsouza/zoxide/releases/tag/v0.9.3 published on 2024-02-13 works as expected today. I guess the Windows system somehow changed and fixed the issue silently.

[LoicRiegel]

If we close this, we could also close duplicate or related issues. #538 was mentioned above for instance, but there might be more.
PR 569 is still in draft and unmerged (commit is from May 2023!) so I have no idea what to do with it