You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just want this to be noted. I see some interest with Windows 10 include BASH.
I try to run PowerShell in Windows Bash cmd. I installed it using the Ubuntu version 14.04.
Commands seem to execute but the screen refresh after running the command won't clear. Also, when you start typing, the prompt is gone and start typing at the top of the screen.
Expected behavior
Normal console behavior after running command the return to the next line of the prompt
Actual behavior
See attached images.
Environment data
Bash - Windows 10 Pro Insider Preview 14901.rs_prerelease.160805-1700
powershell_6.0.0-alpha.8-1_amd64-ubuntu.14.04-x64.deb
>$PSVersionTable
Reacted by Michal Kolarczyk, Espen Wang Andreassen, Rob Cannon, Sergey Tomilin, joshuatee, mtman and Gutemberg Ribeiro
Alpha code running correctly on top of Beta code, eh? You expect a lot. :-) I can't even get a simple ASP.NET Core app (default web template) to run correctly in WSL.
FYI, I get a weird console jitter when through Putty to a Linux server as well - not as bad as it is on Win 10 bash though. It's unusable as Max describes with win10 bash.
Tome Tanasovski (@toenuff) that "weird jitter" has been one of known issues for a long time... but I think it got deleted from the known issues page. We're pretty tied to Console.ReadKey() (unless we want to reimplement that!), and it's a bit slow at times. Do me a favor and file an issue with https://github.com/dotnet/corefx tomorrow 😄
Hey Jaykul, #1088 not a duplicate because its specific to Linux issue and not the Bash on Windows 10. Although I see that the console issue looks identical.
The conhost guys took a look - they think #1877 might be contributing the problem.
I'm working of changing the rendering for multiple reasons, hopefully they're right and my changes will just fix it.
Reacted by Andy Jordan, joshuatee and Nick Bradford
My quick hypothesis is it looks like CursorTop is always zero. We definitely ran into this early on with xterm-like emulators on Linux; perhaps it's recurring with conhost.
I understand that this is meant to be a CLR issue, and that the issue itself is external. But it would for people waiting on this (at least me ;) ) be really nice if we knew when to retry Powershell. Right now it's of no use to me due to these issues alas.
I have to admit that it is sad that this has stalled. The work around still applies and I hope to see this working sometime soon. This is a good opportunity for Windows users using Windows Bash to learn Linux and try PowerShell with it without dealing with building a Linux OS from scratch.
Thanks Andy Jordan (@andschwa)! I got my laptop running Linux with PowerShell since day one. I'm just looking to create awareness with Windows 10 Bash which I already got the workaround doing its magic. No pretty but at least is workable!
I will take your information provided to play with containers later. This is an area I need to tackle soon.
:)
Thanks Andy Jordan (@andschwa)! The main problem is that one Microsoft product (Powershell Core) does not work with other Microsoft product (WSL) harms the reputation of the company despite the fact that the product is still alfa.
Activity
[-]Fix PowerShell in Windows BASH?[/-][+]PowerShell in Windows BASH display issues[/+]rkeithhill commentedon Aug 17, 2016
Alpha code running correctly on top of Beta code, eh? You expect a lot. :-) I can't even get a simple ASP.NET Core app (default web template) to run correctly in WSL.
MaximoTrinidad commentedon Aug 17, 2016
Of course!! Haha!!
At least this is logged. It did load but I want see more!!!!
I'm loving this Linux stuff.
toenuff commentedon Aug 17, 2016
FYI, I get a weird console jitter when through Putty to a Linux server as well - not as bad as it is on Win 10 bash though. It's unusable as Max describes with win10 bash.
andyleejordan commentedon Aug 17, 2016
Tome Tanasovski (@toenuff) that "weird jitter" has been one of known issues for a long time... but I think it got deleted from the known issues page. We're pretty tied to
Console.ReadKey()(unless we want to reimplement that!), and it's a bit slow at times. Do me a favor and file an issue with https://github.com/dotnet/corefx tomorrow 😄Jaykul commentedon Aug 21, 2016
Possibly a dupe of #1088 -- but good detail...
MaximoTrinidad commentedon Aug 21, 2016
Hey Jaykul, #1088 not a duplicate because its specific to Linux issue and not the Bash on Windows 10. Although I see that the console issue looks identical.
I hope this could be fix some time soon.
:)
andyleejordan commentedon Aug 24, 2016
Maximo Trinidad (@MaximoTrinidad) would you please file a bug with BashOnWindows, and reference your issue here? Thanks.
MaximoTrinidad commentedon Aug 24, 2016
Andy Jordan (@andschwa) ... It's done! I logged the issue in BashOnWindows:
PowerShell in Windows BASH display issues when typing cmdlets microsoft/WSL#980
lzybkr commentedon Aug 24, 2016
The conhost guys took a look - they think #1877 might be contributing the problem.
I'm working of changing the rendering for multiple reasons, hopefully they're right and my changes will just fix it.
andyleejordan commentedon Aug 24, 2016
My quick hypothesis is it looks like
CursorTopis always zero. We definitely ran into this early on with xterm-like emulators on Linux; perhaps it's recurring with conhost.lzybkr commentedon Oct 7, 2016
With some help from Mike Griese (@zadjii-msft) and Stephen Toub (@stephentoub), this looks like a CLR issue: https://github.com/dotnet/corefx/issues/12452
lypanov commentedon Jan 9, 2017
I understand that this is meant to be a CLR issue, and that the issue itself is external. But it would for people waiting on this (at least me ;) ) be really nice if we knew when to retry Powershell. Right now it's of no use to me due to these issues alas.
MaximoTrinidad commentedon Jan 9, 2017
I have to admit that it is sad that this has stalled. The work around still applies and I hope to see this working sometime soon. This is a good opportunity for Windows users using Windows Bash to learn Linux and try PowerShell with it without dealing with building a Linux OS from scratch.
:)
iSazonov commentedon Jan 9, 2017
The corefx issue flagged as
Up for Grabs. So don't expect its a quick fix. 😕andyleejordan commentedon Jan 9, 2017
Alexander Kellett (@lypanov), Maximo Trinidad (@MaximoTrinidad), Ilya (@iSazonov), if you want to try out PowerShell on Linux without installing Linux from scratch, perhaps our Linux containers will be of interest to you.
docker run --interactive --tty microsoft/powershell$PSVersionTableHere are our Docker images.
MaximoTrinidad commentedon Jan 9, 2017
Thanks Andy Jordan (@andschwa)! I got my laptop running Linux with PowerShell since day one. I'm just looking to create awareness with Windows 10 Bash which I already got the workaround doing its magic. No pretty but at least is workable!
I will take your information provided to play with containers later. This is an area I need to tackle soon.
:)
Thanks,
Maximo Trinidad
iSazonov commentedon Jan 10, 2017
Thanks Andy Jordan (@andschwa)! The main problem is that one Microsoft product (Powershell Core) does not work with other Microsoft product (WSL) harms the reputation of the company despite the fact that the product is still alfa.
glennsarti commentedon Mar 28, 2017
Confirmed still in an issue in PS 6.0.0-alpha17
glennsarti commentedon Mar 28, 2017
https://github.com/dotnet/corefx/issues/12452 is still open