R
R
Ruslan2015-03-08 00:27:07
Sublime Text
Ruslan, 2015-03-08 00:27:07

Why is there an error trying to parse settings in Sublime text 3?

The essence of the question is this ... When editing the Sublime text 3 settings file, and specifically Preferences.sublime-settings, an error pops up in windows 7x64:

Error trying to parse settings: Expected value in
Packeges\User\Preferences.sublime-settings:1:1

There are no answers to this question on the Internet, although the problem arises. Complete removal of the settings file helps to get rid of the error. No other way. Even rolling back to a file without settings does not help fix the error. The error appears both on the portable version and on the installed one. The same thing on Sublime text 2. Help me solve the problem, the editor is good. And yet, sometimes when you remove it again and then install it, the default settings file is not edited. Artificial creation helps.
If decrypted, then a type error occurs in the first line of the first column of this file. But everything is much more complicated. For example, I open the settings file, enter a line of parameters, save. All OK. I open again, re-save, again everything is OK. I repeat the procedure, for example, one more time, and an error pops up. Those. in fact, it doesn’t matter whether you add something to this file or just re-save it, the error still appears.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
R
Ruslan, 2015-03-09
@Tutorian

The problem was solved by changing the encoding to pure UTF-8. Thanks to everyone who signed up!

A
Andrey Dyrkov, 2015-03-08
@VIKINGVyksa

The settings file was incorrectly edited, maybe you put an extra comma or something else, attach your settings to the question or look for the error yourself.

A
Alexander Ruchkin, 2015-03-09
@VoidEx

The impression is that the encoding is UTF-16 with BOM. I checked myself - yes. If you select "Save with encoding" and select some UTF with BOM - it does not read. Resave to just UTF-8: "Save with encoding - UTF-8"

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question