Summary
Taste Learner appears to have used some illegal characters for Windows resulting in an error. Command code was able to help guide me through fixing it, and suggested that I report it here to be fixed. It's suggestion is pasted below:
the learner should sanitize Windows-illegal characters like * and : before building a path
Expected Behavior
Taste file written with tastes.
Actual Behavior
taste learning failed: ENOENT: no such file or directory, mkdir
'C:\Users\user.commandcode\taste--taste-learned.-confidence:-0.85'
(the error was copied and pasted. The user and taste were replaced with placeholders )
Steps to reproduce the issue
Use command code on Windows using Windows Terminal (would have filled in the Terminal/IDE field below, but it's stuck on 'Unknown" for some unknown reason -- pun intended, but nonetheless irritating)
Command Code Version
1.73.0
Operating System
Windows
Terminal/IDE
Unknown
Shell
cmd.exe
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
No response
Summary
Taste Learner appears to have used some illegal characters for Windows resulting in an error. Command code was able to help guide me through fixing it, and suggested that I report it here to be fixed. It's suggestion is pasted below:
the learner should sanitize Windows-illegal characters like * and : before building a pathExpected Behavior
Taste file written with tastes.
Actual Behavior
taste learning failed: ENOENT: no such file or directory, mkdir
'C:\Users\user.commandcode\taste--taste-learned.-confidence:-0.85'
(the error was copied and pasted. The user and taste were replaced with placeholders )
Steps to reproduce the issue
Use command code on Windows using Windows Terminal (would have filled in the Terminal/IDE field below, but it's stuck on 'Unknown" for some unknown reason -- pun intended, but nonetheless irritating)
Command Code Version
1.73.0
Operating System
Windows
Terminal/IDE
Unknown
Shell
cmd.exe
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
No response