Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setting.json property expected(bug) #66831

Closed
euntaek opened this issue Jan 21, 2019 · 2 comments
Closed

setting.json property expected(bug) #66831

euntaek opened this issue Jan 21, 2019 · 2 comments

Comments

@euntaek
Copy link

euntaek commented Jan 21, 2019

Issue Type: Bug

The setting.json is in error.
I want to correct the error. settings.json is read-only and cannot be modified.
Please help me.

error images

VS Code version: Code 1.30.2 (61122f8, 2019-01-07T22:48:31.260Z)
OS version: Darwin x64 18.2.0

System Info
Item Value
CPUs Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (4 x 2000)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 3
Memory (System) 8.00GB (3.54GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (14)
Extension Author (truncated) Version
bracket-pair-colorizer-2 Coe 0.0.25
vscode-eslint dba 1.8.0
githistory don 0.4.4
vsc-material-theme Equ 2.6.3
RelativePath jak 1.4.0
HTMLHint mka 0.5.0
vscode-language-pack-ko MS- 1.30.2
debugger-for-chrome msj 4.11.1
material-icon-theme PKi 3.6.2
LiveServer rit 5.3.1
ActiveFileInStatusBar Ros 1.0.3
code-settings-sync Sha 3.2.4
markdown-all-in-one yzh 2.0.1
html-css-class-completion Zig 1.17.1

(1 theme extensions excluded)

@euntaek
Copy link
Author

euntaek commented Jan 21, 2019

Resolved.
Errors disappear after deleting Korean Language Pack for Visual Studio Code extensions .

@sandy081
Copy link
Member

Closing this issue as it is resolved.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@sandy081 @euntaek and others