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

The encoding of files changes upon opening, for Sublime configuration files. #2953

Open
Mnior opened this issue Aug 28, 2019 · 3 comments

Comments

@Mnior
Copy link

commented Aug 28, 2019

In addition to the "bug", UTF-8 with BOM set in the parameter default_encoding leads to annoying rollback of the encoding of configuration files during editing. Later errors fly out: Error on Save config or start Sublime Text 3

Steps to reproduce

  1. Open: Main Menu Preferences -> Settings.
  2. Add "default_encoding": "UTF-8 with BOM",. Save & Close.
  3. Retry open: Main Menu Preferences -> Settings. And Save as is.

Expected behavior

The file encoding remains UTF-8.

Actual behavior

The file encoding has changed from UTF-8 to UTF-8 with BOM and error pops up.

Environment

  • Build: 3207
  • OS and version: Windows 10, version 1903, build 18362.295

Related links

Problem with "default_encoding": "UTF-8 with BOM"

How to get around

  1. Open: Main Menu Preferences -> Settings. Or any JSON file.
  2. Open: Main Menu Preferences -> Settings - Syntax Specific
  3. Add "default_encoding": "UTF-8",. Save in UTF-8 encoding & Close.

It would be nice to have Sublime Text always save all its configuration files in UTF-8, regardless of the default_encoding parameter.

@FichteFoll

This comment has been minimized.

Copy link
Member

commented Aug 28, 2019

Imo this is entering duplicate territory, since this issue is a direct result of the referenced one, but I'll leave that for someone else to decide.

@evandrocoan

This comment has been minimized.

Copy link

commented Aug 28, 2019

Imo this is entering duplicate territory, since this issue is a direct result of the referenced one,

We can call this a feature request:

It would be nice to have Sublime Text always save all its configuration files in UTF-8, regardless of the default_encoding parameter.

@FichteFoll

This comment has been minimized.

Copy link
Member

commented Sep 11, 2019

Supposedly fixed in the next build where ST will ignore BOMs in its config files.

@FichteFoll FichteFoll added this to the Build 3209 milestone Sep 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.