starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows WSL Ubuntu opening PowerShell doesn't have autocomplete #175

New Issue
Closed
opened 2026-01-30 21:44:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:44:39 +00:00
Owner
Copy Link

Originally created by @J0rdyV on GitHub (Mar 2, 2018).

I configured my ubuntu terminal in ~/.bash_aliases with

alias powershell="/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe"

So that when i'm in a folder an quickly want to execute a PowerShell command, i can do so with just typing powershell, and a it opens inside the folder.

This works perfectly, commands also execute like i want, no problems there.
But i don't have autocomplete.
Also arrow up, for last commands doesn't work.
Autocomplete is enabled in ~/.bashrc and works for linux commands.

Is this issue because i'm opening it from bash?
Or can i configure this option somewhere so powershell opens in a different mode when i can use the arrow keys, autocomplete, ...

I know there is a linux powershell, but this does not have the functionality i need.

Windows build: 1709 (16299.248)
Kernel: x86_64 Linux 4.4.0-43-Microsoft
Shell: bash 4.3.48

Originally created by @J0rdyV on GitHub (Mar 2, 2018). I configured my ubuntu terminal in *~/.bash_aliases* with ``` alias powershell="/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe" ``` So that when i'm in a folder an quickly want to execute a PowerShell command, i can do so with just typing powershell, and a it opens inside the folder. This works perfectly, commands also execute like i want, no problems there. But i don't have autocomplete. Also arrow up, for last commands doesn't work. Autocomplete is enabled in *~/.bashrc* and works for linux commands. Is this issue because i'm opening it from bash? Or can i configure this option somewhere so powershell opens in a different mode when i can use the arrow keys, autocomplete, ... I know there is a linux powershell, but this does not have the functionality i need. Windows build: 1709 (16299.248) Kernel: x86_64 Linux 4.4.0-43-Microsoft Shell: bash 4.3.48
claunia added the Product-WSLArea-Interop labels 2026-01-30 21:44:39 +00:00
claunia commented 2026-01-30 21:44:40 +00:00
Author
Owner
Copy Link

@parkovski commented on GitHub (Mar 5, 2018):

This is due to lack of interop/Windows PTY support. It's coming, but currently not possible without workarounds like winpty.

@parkovski commented on GitHub (Mar 5, 2018): This is due to lack of interop/Windows PTY support. It's coming, but currently not possible without workarounds like winpty.
claunia commented 2026-01-30 21:44:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 6, 2018):

@parkovski is right. Interactive interop scenarios are pretty limited for the time being.

@zadjii-msft commented on GitHub (Mar 6, 2018): @parkovski is right. Interactive interop scenarios are pretty limited for the time being.
claunia commented 2026-01-30 21:44:40 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (May 3, 2018):

Hey @J0rdyV - a few things here:

  1. You don't need to absolute-path things that are on your Windows path because we add the Windows path to your Linux path by default
  2. Windows cannot (currently) access Linux folders/files so if you start PowerShell in /… or ~/..., your PowerShell instance will start in the system folder. We're working to improve this in the future (no ETA at present).
  3. You should see better support for cursor keys and autocomplete in Win10 v1803 Spring 2018 Update & later builds.

Closing for now - please file a separate issue for each individual issue to avoid too much crossing of the streams ;)

@bitcrazed commented on GitHub (May 3, 2018): Hey @J0rdyV - a few things here: 1. You don't need to absolute-path things that are on your Windows path because we add the Windows path to your Linux path by default 1. Windows cannot (currently) access Linux folders/files so if you start PowerShell in `/…` or `~/...`, your PowerShell instance will start in the system folder. We're working to improve this in the future (no ETA at present). 1. You should see better support for cursor keys and autocomplete in Win10 v1803 Spring 2018 Update & later builds. Closing for now - please file a separate issue for each individual issue to avoid too much crossing of the streams ;)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Interop Product-WSL
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#175
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?