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

REPL / shells installed from store (non-linux / non-MS) not added to the new terminal #8381

Closed
bhramchari opened this issue Nov 24, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bhramchari
Copy link

Screenshot 2020-11-23 175922

REPL / shells installed from store (non-linux / non-MS) not added to the new Terminal. Attached image for reference, can this be fixed/enabled/added in future releases ? Due to this limitation we can't use the new Terminal to access Python or other shells installed from the Store.

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
❯ [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0

Windows Terminal version (if applicable): Version: 1.4.3243.0

Any other software? 
Python 3.7 installed from the MS Store, PS Core 7.1 from MS Store

Steps to reproduce

Install Python from the Store

Expected behavior

With the new terminal ver 1.4+ the jumplist and other options should auto-populate the new options

Actual behavior

Python 3.7 is not accessible from the new Terminal app, it launches its own console upon launching

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 24, 2020
@DHowett
Copy link
Member

DHowett commented Nov 24, 2020

Alright, so..

  1. The jumplist only updates when Terminal is launched
  2. We autodetect like 7 different shells right now
  3. If we keep autodetecting more, we're going to start driving users CRAZY (!)
  4. There's a couple requests kicking around for this, but the one that is important is Proto extensions spec #7584 (spec) which will let Python tell us where it is. That's going to be easier than us searching high and low to find it.

/dup #7584

@ghost
Copy link

ghost commented Nov 24, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Nov 24, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 24, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants