Skip to content

'screen' is incompatible with PowerShell #2364

Closed

Description

Repro:

Ubuntu 14.04

powershell
sudo apt-get install screen
screen
ls

Expected:
prompt to come back

Actual:
hangs on output

Removing PSReadline doesn't change the result. Ctrl-A then k to kill the current screen session.

Name                           Value
----                           -----
PSVersion                      6.0.0-alpha
PSEdition                      Core
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   3.0.0.0
GitCommitId                    v6.0.0-alpha.10
CLRVersion
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Activity

  1. MaximoTrinidad commented on Sep 26, 2016

    @MaximoTrinidad

    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.

    setaliasls

    setaliasls2

  2. SteveL-MSFT commented on Sep 27, 2016

    @SteveL-MSFT
    MemberAuthor

    Maximo Trinidad (@MaximoTrinidad) the issue is specific to using native commands within PowerShell within Screen

  3. MaximoTrinidad commented on Sep 27, 2016

    @MaximoTrinidad

    Thanks for clarifying!
    :)

  4. andyleejordan commented on Sep 27, 2016

    @andyleejordan
    Member

    Ah, I was able to repro this. Definitely strange. But it does work correctly inside tmux.

    Even weirder: executing $env:TERM totally worked: it executed, printed screen as expected, and the prompt displayed afterward no problem.

  5. MaximoTrinidad commented on Sep 28, 2016

    @MaximoTrinidad

    Ah! I didn't have 'screen' installed. After I install it, I went through the steps:

    1. Open Terminal
    2. Run powershell
    3. At powershell prompt, execute screen
    4. in screen Bash prompt (within powershell)
    5. Run a Linux command ' ls ' then exit.
    6. Goes back to powershell prompt.

    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.

    screenissue

  6. added this to the milestone on Sep 28, 2016
  7. SteveL-MSFT commented on Sep 29, 2016

    @SteveL-MSFT
    MemberAuthor

    repros for me on 16.04 and alpha.10

  8. SteveL-MSFT commented on Sep 29, 2016

    @SteveL-MSFT
    MemberAuthor

    Maximo Trinidad (@MaximoTrinidad) in your repro screenshot, it shows that "screen is terminating" which may explain why it didn't repro for you

  9. MaximoTrinidad commented on Sep 29, 2016

    @MaximoTrinidad

    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.

    :)

  10. modified the milestones: , on Dec 19, 2016
  11. ealexjordan commented on Mar 15, 2017

    @ealexjordan
    Contributor

    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.

  12. removed their assignment
    on Mar 15, 2017
  13. modified the milestones: 6.0.0-beta1, on Mar 16, 2017
  14. SteveL-MSFT commented on Apr 24, 2017

    @SteveL-MSFT
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions