-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Tasks should support specifying the output encoding #3550
Comments
For sure we're blindly converting to/from |
+1 . hope to fix as soon as possible |
+2. It's really a boring bug, hope to get it down in the next release version. 🎱 |
Please see #15179. The idea here to move forward is to execute tasks in the terminal instead in its own output channel. |
Have the same problem Win10/Russian MsBuild. Really annoying. |
Agree. The plan forward here is to use the integrated terminal to run tasks. This will make this work and even support input and ANSI control characters |
Why is it a "feature-request"? Not garbling an output is not a feature. I think it should be "bug" and "important". |
In tasks.json: "command": "cmd",
"args": ["/c chcp 65001 >nul && mingw32-make"] instead of "command": "mingw32-make" and everything seems to work fine.
|
@eternalphane thanks for this. Actually I am working on support for running tasks in the integrated terminal which should make the encoding problem go away. |
@dbaeumer update on this feature would be much appreciated. Not being able to figure out what the error message is makes the task feature almost unusable, thanks. |
@gyuhyeon this will be addressed by using the terminal as the execution engine for tasks. You can alreadz opt into using the terminal by adding |
"runner":"terminal" does not appear to work anymore, I have had success setting the ENV before my command. I am on a Mac. I was trying to run Jekyll.
|
@rajannpatel strange, |
I have a workaround for this issue here: |
Thanks! |
[Addressed in new terminal runner] In the new terminal runner with can be controlled by configuring the shell to be used in the tasks.json. This allows to control the encoding. |
I am closing this issue since this can now be control using normal Terminal setups in task 2.0.0. I also wrote some doc explaining how this is best used here: https://github.com/Microsoft/vscode-docs/blob/vnext/docs/editor/tasks.md#changing-the-encoding-for-a-task-output I will close the issue. Please reopen a new issue against the current support if it is not satisfactory for you. |
I think it's related to some global language problem.
The output message is broken like this
'luac'��(��) ���� �Ǵ� �ܺ� ����, ������ �� �ִ� ���α�, �Ǵ�
��ġ ������ �ƴմϴ�.
P.S> My environment is Win10 Ko(Korean version)
https://onedrive.live.com/redir?resid=73F0A5AA67A0D48F!212183&authkey=!ACjcDNvjj7PjRmY&v=3&ithint=photo%2cpng
The text was updated successfully, but these errors were encountered: