-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Allow to save with UTF-8 + BOM encoding #751
Comments
👍 |
I mean 👍 for having such an option, but 👎 for any tool that needs BOMs :) |
@bpasero LOL, like powershell. |
My strong position against BOMs is company agnostic ;) |
. |
I want to this feature too |
I really need this encoding type too. Is it planned in a future release? |
need too :[ |
Having this capability would unblock PowerShell Script Analyzer identifying a Warning for new scripts authored using VSCode. |
Pushed a change that allows to set a new setting
|
👍 |
Discussed with the team and we favor a different approach that does not include a new setting, instead we piggy back on the existing encoding option and add a new option
|
Now is better! you have to be able to save with BOM and save with BOM if the file already has it. |
In version 0.10.2 I am having issues with making sure a file is saved with UTF-8 and BOM character encoding.
Please add such an option.
The text was updated successfully, but these errors were encountered: