Skip to content
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

'screen' is incompatible with PowerShell #2364

Closed
SteveL-MSFT opened this issue Sep 26, 2016 · 10 comments
Closed

'screen' is incompatible with PowerShell #2364

SteveL-MSFT opened this issue Sep 26, 2016 · 10 comments
Assignees
Labels
Resolution-Answered The question is answered. WG-Interactive-Console the console experience
Milestone

Comments

@SteveL-MSFT
Copy link
Member

SteveL-MSFT commented Sep 26, 2016

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
@SteveL-MSFT SteveL-MSFT added the WG-Interactive-Console the console experience label Sep 26, 2016
@MaximoTrinidad
Copy link

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

@SteveL-MSFT
Copy link
Member Author

@MaximoTrinidad the issue is specific to using native commands within PowerShell within Screen

@MaximoTrinidad
Copy link

Thanks for clarifying!
:)

@andyleejordan
Copy link
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.

@MaximoTrinidad
Copy link

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

@SteveL-MSFT SteveL-MSFT added this to the 6.0.0 milestone Sep 28, 2016
@SteveL-MSFT
Copy link
Member Author

SteveL-MSFT commented Sep 29, 2016

repros for me on 16.04 and alpha.10

@SteveL-MSFT
Copy link
Member Author

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

@MaximoTrinidad
Copy link

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.

:)

@SteveL-MSFT SteveL-MSFT modified the milestones: 6.0.0-beta, 6.0.0 Dec 19, 2016
@ealexjordan ealexjordan added Area-Maintainers-Documentation specific to documentation in this repo and removed WG-Interactive-Console the console experience labels Mar 15, 2017
@ealexjordan
Copy link
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.

@ealexjordan ealexjordan removed their assignment Mar 15, 2017
@SteveL-MSFT SteveL-MSFT modified the milestones: 6.0.0-beta1, 6.0.0-beta2 Mar 16, 2017
@SteveL-MSFT SteveL-MSFT self-assigned this Apr 24, 2017
@SteveL-MSFT SteveL-MSFT added WG-Interactive-Console the console experience Resolution-Answered The question is answered. and removed Area-Maintainers-Documentation specific to documentation in this repo labels Apr 24, 2017
@SteveL-MSFT
Copy link
Member Author

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
Labels
Resolution-Answered The question is answered. WG-Interactive-Console the console experience
Projects
Development

No branches or pull requests

4 participants