-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Console not working on Windows 10 1809 update #501
Comments
Please fill the issue by following the template. |
Edited my issue |
Same also happens in Visual Studio Code's terminal. microsoft/vscode#57803 |
Having the same issue, the window opens scrolled to the bottom cutting off the text |
I get this sporadically, in my case I think it's because of some DPI funkyness in that my monitors have different DPI... so depending what monitor I opened the tab then move it to another on it behaves differently. |
When I increase the windows size properties the issue is also gone. Is this a Windows 'bug' or a Console issue? |
It seems that Android Studio for Windows also has this issue. It may be a Windows bug. |
This is a known Windows bug that should be fixed in the next major release for legacy code, and they expect to also release a new PTY API that should allow for drastic improvement in console type programs that use it, which will also not suffer from this bug. |
ConEmu doesn't appear to have this issue with cmd.exe. What is it doing differently? |
Actually the problem is the same with EVERY TERMINAL (conemu, bash, git bash, cmd, powershell, etc...) when used "integrated" with ANY EDITOR (vscode, atom, sublimetext, etc) it's a Windows terminal API problem that (re-)appeared with last windows update. Best solution: a Linux virtual machine (VirtualBox or VMware) A shame that Microsoft after almost 40 years is still not able to make a simple terminal program work !!! How can we trust them with a full OS ???? |
The VSCode issue referenced above was fixed by enabling support for the new ConPTY system. Introduction to ConPTY: So existing apps should either update to support ConPTY or wait for backward compatibility fix. What's the current plan? Quote from the link above:
|
I have updated my WIndows 10 to version 1809. When I open Console I get a black console window without a path visible. When I press a key the path becomes visible,
Expected Behavior
When I open the executable I want to see the path of the directory were console is started
Actual Behavior
When I open the executable I don't see the path untill I press a key
Steps to reproduce
Open the executable
Diagnostic Report
Crash Report
No crash
The text was updated successfully, but these errors were encountered: