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 will have to say that's possible nothing is wrong because PowerShell version 6.0.0-Alpha.10 doesn't include the Alias " ls " for Get-ChildItem. It may be implemented later
You can do a "Set-Alias ls Get-ChildItem" and then you can run " ls " at the PowerShell prompt.
You have to forgive me. I've been working with Linux for the since and learn a lot. Before, I didn't that Screen installed and when I typed Screen nothing happen (no errors).
So, after I installed Screen, I thought the behavior of [screen is terminating] within PowerShell was correct. Now, I can use Screen within PowerShell. Is cool to go back and forth with it.
Only native commands hang, due to an escape character being improperly read by screen. Can repro this in Mobaxterm on Centos and Ubuntu, and on bare metal Ubuntu. Cannot repro this in Hyper-V, tmux, dvmt, and cannot repro on anything with term set to xterm-256color (or term other than screen) in .screenrc.
There are a number of bugs filed with GNU screen that this could be related to (https://savannah.gnu.org/bugs/?42342).
I'm reassigning to documentation. It should be documented that term needs to be properly set in .screenrc for the PowerShell console to properly work.
Activity
MaximoTrinidad commentedon Sep 26, 2016
I will have to say that's possible nothing is wrong because PowerShell version 6.0.0-Alpha.10 doesn't include the Alias " ls " for Get-ChildItem. It may be implemented later
You can do a "Set-Alias ls Get-ChildItem" and then you can run " ls " at the PowerShell prompt.
This is on my Ubuntu 16.04.1 LTS Desktop.
SteveL-MSFT commentedon Sep 27, 2016
Maximo Trinidad (@MaximoTrinidad) the issue is specific to using native commands within PowerShell within Screen
MaximoTrinidad commentedon Sep 27, 2016
Thanks for clarifying!
:)
andyleejordan commentedon Sep 27, 2016
Ah, I was able to repro this. Definitely strange. But it does work correctly inside
tmux.Even weirder: executing
$env:TERMtotally worked: it executed, printedscreenas expected, and the prompt displayed afterward no problem.MaximoTrinidad commentedon Sep 28, 2016
Ah! I didn't have 'screen' installed. After I install it, I went through the steps:
It works for me without any additional changes after installing 'screen'.
This is on my Ubuntu 16.04.1 LTS Desktop, and PowerShell 6.0.0-alpha.10.
SteveL-MSFT commentedon Sep 29, 2016
repros for me on 16.04 and alpha.10
SteveL-MSFT commentedon Sep 29, 2016
Maximo Trinidad (@MaximoTrinidad) in your repro screenshot, it shows that "screen is terminating" which may explain why it didn't repro for you
MaximoTrinidad commentedon Sep 29, 2016
Hi Steve!
You have to forgive me. I've been working with Linux for the since and learn a lot. Before, I didn't that Screen installed and when I typed Screen nothing happen (no errors).
So, after I installed Screen, I thought the behavior of [screen is terminating] within PowerShell was correct. Now, I can use Screen within PowerShell. Is cool to go back and forth with it.
:)
ealexjordan commentedon Mar 15, 2017
Only native commands hang, due to an escape character being improperly read by screen. Can repro this in Mobaxterm on Centos and Ubuntu, and on bare metal Ubuntu. Cannot repro this in Hyper-V, tmux, dvmt, and cannot repro on anything with term set to xterm-256color (or term other than screen) in .screenrc.
There are a number of bugs filed with GNU screen that this could be related to (https://savannah.gnu.org/bugs/?42342).
I'm reassigning to documentation. It should be documented that term needs to be properly set in .screenrc for the PowerShell console to properly work.
SteveL-MSFT commentedon Apr 24, 2017
This is no longer repro'ing for me on Ubuntu16 and alpha.18. TERM is set to xterm-256color, so maybe Ubuntu changed the default on an update.