starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Settings returns "SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data" #10740

New Issue
Closed
opened 2026-01-31 02:28:58 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:28:58 +00:00
Owner
Copy Link

Originally created by @marinsteve on GitHub (Sep 24, 2020).

Environment

Windows build number: Version 10.0.19041.508
Windows Terminal version :1.3.2651.0

Any other software?
Firefox 81 (default file association with json)

Steps to reproduce

Install 1.3.2651.0, from Microsoft Store. Launch, and click Settings.

Expected behavior

Display of the default auto-generated settings.json file.

Actual behavior

Firefox displays:
in JSON tab: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
in Raw Data tab, the ordinary default settings.json file appears
Screenshots:
error
rawdata

Note: deleting the settings.json file causes terminal to regenerate the unparsable json file

Originally created by @marinsteve on GitHub (Sep 24, 2020). # Environment Windows build number: Version 10.0.19041.508 Windows Terminal version :1.3.2651.0 Any other software? Firefox 81 (default file association with json) # Steps to reproduce Install 1.3.2651.0, from Microsoft Store. Launch, and click Settings. # Expected behavior Display of the default auto-generated settings.json file. # Actual behavior Firefox displays: in JSON tab: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data in Raw Data tab, the ordinary default settings.json file appears Screenshots: ![error](https://user-images.githubusercontent.com/5280804/94088338-1a4f2300-fdc5-11ea-9106-a1a78ecafc0f.jpg) ![rawdata](https://user-images.githubusercontent.com/5280804/94088447-600beb80-fdc5-11ea-9121-e1a2fb5fc68e.jpg) Note: deleting the settings.json file causes terminal to regenerate the unparsable json file
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:28:59 +00:00
claunia commented 2026-01-31 02:28:59 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 24, 2020):

The settings file format isn't pure JSON - it's a superset of JSON that allows for comments. Since Firefox is expecting the content to be pure JSON, it identifies the comment on the first line as a syntax error.

@j4james commented on GitHub (Sep 24, 2020): The settings file format isn't pure JSON - it's a superset of JSON that allows for comments. Since Firefox is expecting the content to be pure JSON, it identifies the comment on the first line as a syntax error.
claunia commented 2026-01-31 02:29:00 +00:00
Author
Owner
Copy Link

@marinsteve commented on GitHub (Sep 25, 2020):

Thanks. I'll killed the comments by editing it in vim, and it works.

@marinsteve commented on GitHub (Sep 25, 2020): Thanks. I'll killed the comments by editing it in vim, and it works.
claunia commented 2026-01-31 02:29:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 25, 2020):

Sorry -- I meant to click the text box (not "Close", though that's coming)

Firefox isn't really a suitable JSON editor -- what're you trying to do with it?

If it's your default association for JSON files, that's going to pose a problem for actually editing them! 😄

@DHowett commented on GitHub (Sep 25, 2020): Sorry -- I meant to click the text box (not "Close", though that's coming) Firefox isn't really a suitable JSON editor -- what're you trying to do with it? If it's your default association for JSON files, that's going to pose a problem for actually editing them! :smile:
claunia commented 2026-01-31 02:29:01 +00:00
Author
Owner
Copy Link

@marinsteve commented on GitHub (Sep 25, 2020):

I didn't explicitly choose Firefox as the association for json. I'm not
sure how it got set that way. I've fixed it to be associated with vim,
which does a good job, even though it flags //comments. At least it lets
me write comments, and save json files that work.

Thanks for finding a weird one.

@marinsteve commented on GitHub (Sep 25, 2020): I didn't explicitly choose Firefox as the association for json. I'm not sure how it got set that way. I've fixed it to be associated with vim, which does a good job, even though it flags //comments. At least it lets me write comments, and save json files that work. Thanks for finding a weird one.
claunia commented 2026-01-31 02:29:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 25, 2020):

I'm quite surprised about that! We'll hopefully address this better with #1564 (the settings UI)... 😄 Some day soon . . .

I'll close this one out as question/answered for now. Thanks for flagging us down!

@DHowett commented on GitHub (Sep 25, 2020): I'm quite surprised about that! We'll hopefully address this better with #1564 (the settings UI)... :smile: Some day soon . . . I'll close this one out as question/answered for now. Thanks for flagging us down!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Needs-Tag-Fix Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10740
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?