[Bug]: stdin for path not working on windows anymore

[dekaravanhoc]

Kind of Issue

Change in behavior / Regression

Tool or Library

cspell

Version

8.14.4

Supporting Library

No response

OS

Windows

OS Version

Windows 11

Description

Hi,

https://github.com/davidmh/cspell.nvim uses the stdin feature to get spellchecking on the current opened file.
But on Windows using stdin with a path returns Linter Error: Invalid URL.
That worked on older versions up to 8.11.0

Steps to Reproduce

1. cspell stdin://C:\Users\XXX\AppData\Local\nvim\lua\package_manager\init.lua (or any other file)
2. Error pops up.

(Tried different formating for the Slashes all the same. The above did still work up till version 8.11.0.

Expected Behavior

Correct output for spellcheck.

Additional Information

No response

cspell.json

No response

cspell.config.yaml

No response

Example Repository

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[Jason3S]

@dekaravanhoc,

Thank you. I had not realized that had broken on Windows.

[Jason3S]

Sorry for taking so long, I had to get access to a Windows machine to see what is going on.

The workaround is to use three slashes: stdin:///C:/Users/XXX/AppData/Local/nvim/lua/package_manager/init.lua.

I'll see if I can adjust the parser to have the old behavior work.

From 8.11 the spell checker started using URLs internally. The NodeJS URL parser does something weird with just 2 slashes.

[Jason3S]

The workaround is to use three slashes: stdin:///C:/Users/XXX/AppData/Local/nvim/lua/package_manager/init.lua.

I should have tested it before I wrote it. This doesn't work. I'll look for a fix in the code.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.