We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure if we already do this or if it's possible, but we've had a few issues to do with encoding.
Ideally that information should just be in the logs.
Specifically we should add:
"files.encoding"
$OutputEncoding
Thoughts? Any other suggestions?
The text was updated successfully, but these errors were encountered:
Also add the full version (+ prerelease suffix) in the log file (PowerShell/PowerShellEditorServices#770).
Sorry, something went wrong.
It looks like getting VSCode's file encoding configuration may not currently be possible: microsoft/vscode#824
Unassigning myself since I've done all the work I think that can be done on this for the moment.
Leaving the issue open to track adding in VSCode's encoding configuration.
No branches or pull requests
Not sure if we already do this or if it's possible, but we've had a few issues to do with encoding.
Ideally that information should just be in the logs.
Specifically we should add:
"files.encoding"
to the VSCode extension logs$OutputEncoding
(and possibly others) to the EditorServices logsThoughts? Any other suggestions?
The text was updated successfully, but these errors were encountered: