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

Closed
opened 2026-01-31 02:50:56 +00:00 by claunia · 2 comments
Owner

Originally created by @bhramchari on GitHub (Nov 24, 2020).

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

Originally created by @bhramchari on GitHub (Nov 24, 2020). ![Screenshot 2020-11-23 175922](https://user-images.githubusercontent.com/43825927/100028961-bb525e00-2db5-11eb-933f-a4187b37a8d5.jpg) <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> 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 ```none 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
claunia added the Resolution-Duplicate label 2026-01-31 02:50:56 +00:00
Author
Owner

@DHowett commented on GitHub (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 #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

@DHowett commented on GitHub (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 #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
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11551