Closed xymunter closed 6 months ago
Okay, now I feel very silly. I wanted to point out a log entry marked as "ERROR" and found another, very specific error message: [DEBUG] 11:06:39.912 config.go:loadConfig:163 → error decoding config file: invalid character '/' looking for beginning of value
So I looked into my template, and found that I had commented out some stuff, using '// ....'. After removing that, the config could be reloaded again.
@xymunter you have a comment in your json
config. That's not accepted, so you'll need to change your file extension to jsonc
and this will work.
I suspect this will be a very common issue
yes, it seems like I will have to make that the default behaviour for json
, even if it's completely against the spec :-)
I had the same issue as well. Pinning this issue, and maybe adding something to the release notes / documentation would probably be a good idea
@Lightfire228 I'm going to strip comments regardless ;-) See #4763
Good thing I looked into the issues :D
After updating yesterday and greeted with the error message afterwards I was now prepared to dig for the failure. Saved a lot of time :D
And TIL something new about json
.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
I was upgrading my installed version (19.11.7) to the new version my MS Terminal showed me - which was 19.15.1 at the time -(although a newer release 19.16.0 is shown here at the time I'm writing this) using winget.
The installation process didn't show any errors. However, I was greeted with a "Config Error" and a different (fallback?) theme:
I haven't changed anything to the used theme since I first customized it months ago.
Theme
Customized "slimfat.omp.json"
What OS are you seeing the problem on?
No response
Which shell are you using?
No response
Log output