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

Powershell hot key ctrl j and ctrl w #5472

New Issue
Open
opened 2026-01-31 00:14:13 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:14:13 +00:00
Owner
Copy Link

Originally created by @Xdminsy on GitHub (Dec 9, 2019).

#Environment

Windows build number: Microsoft Windows [Version 10.0.18362.356]
Windows Terminal version (if applicable): 0.7.3382.0


Any other software?
Powershell Core: 7.0.0-preview.6

I used to bind ctrl+j to enter and use ctrl+w to backward delete word. I have

Set-PSReadLineOption -BellStyle None -EditMode Emacs

emacs edit mode enabled in my powershell.
The ctrl+w works differently in powershell and in powershell in windows terminal.
If I input Get-Command and type ctrl+w, only the Command wil be deleted in powershell.
But in Windows terminal the Get- will be deleted as well.
I don't understand why, but if I explicitly add this to $PROFILE

Set-PSReadLineKeyHandler -Chord ctrl+w -Function BackwardDeleteWord

It works in terminal as expected.

Though ctrl+w can work as expected if I add one line, the ctrl+j cannot work,

Set-PSReadLineKeyHandler -Chord ctrl+j -Function AcceptLine

In powershell I can use ctrl+j instead of Enter key to run command.
But in powershell in Windows Terminal this doesn't work, ctrl+j do nothing even if I mapped it to something.
Other keys seem to work, I only found the binding for ctrl+j won't work.
I thought terminal deals with ctrl+j itself instead of sending it to powershell, but I tried mapping ctrl+j in vim running in terminal it worked.

So I don't understand why these happen, why?

Originally created by @Xdminsy on GitHub (Dec 9, 2019). #Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.356] Windows Terminal version (if applicable): 0.7.3382.0 Any other software? Powershell Core: 7.0.0-preview.6 ``` I used to bind ctrl+j to enter and use ctrl+w to backward delete word. I have ```powershell Set-PSReadLineOption -BellStyle None -EditMode Emacs ``` emacs edit mode enabled in my powershell. The ctrl+w works differently in powershell and in powershell in windows terminal. If I input `Get-Command` and type ctrl+w, only the `Command` wil be deleted in powershell. But in Windows terminal the `Get-` will be deleted as well. I don't understand why, but if I explicitly add this to $PROFILE ```powershell Set-PSReadLineKeyHandler -Chord ctrl+w -Function BackwardDeleteWord ``` It works in terminal as expected. Though ctrl+w can work as expected if I add one line, the ctrl+j cannot work, ```powershell Set-PSReadLineKeyHandler -Chord ctrl+j -Function AcceptLine ``` In powershell I can use ctrl+j instead of Enter key to run command. But in powershell in Windows Terminal this doesn't work, ctrl+j do nothing even if I mapped it to something. Other keys seem to work, I only found the binding for ctrl+j won't work. I thought terminal deals with ctrl+j itself instead of sending it to powershell, but I tried mapping ctrl+j in vim running in terminal it worked. So I don't understand why these happen, why?
claunia added the Resolution-Duplicate label 2026-01-31 00:14:13 +00:00
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 Resolution-Duplicate
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#5472
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?