BackwardKillWord bound to Escape,Backspace not working
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by reproducing the Escape,Backspace chord and inspecting the behavior reported by Get-PSReadLineKeyHandler. Trace the key-handler and terminal input handling for Backspace, comparing it with the working Escape,Delete binding. Done means Escape,Backspace invokes BackwardKillWord and deletes the preceding word without breaking the other Escape bindings.
Written by the indexing model from the issue text.
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
I believe this is a default KeyHandler, but ESC-Backspace is no longer working for me. The other handlers using Escape all seem to work (ESC-u and ESC-l to upper/lowercase a word, ESC-b and ESC-f to move forward/backword by word, ESC-d to forward kill a word, etc.). But ESC-Backspace just does ... nothing.
I set a new handler for 'Escape,Delete' to do a BackwardKillWord and that works, so it seems the problem is something with my Escape key.
My backspace in a normal terminal sends a Ctrl-H. It's been that way for years, but this stopped working a couple months ago.
Expected behavior
Pressing Escape,Backspace should delete the word before the current cursor location.
Actual behavior
Nothing happens.
Error details
No error is produced.
Environment data
PS> get-psReadLineKeyHandler -Chord "Escape,Backspace"
Basic editing functions
=======================
Key Function Description
--- -------- -----------
Escape,Backspace BackwardKillWord Move the text from the start of the current
or previous word to the cursor to the kill
ring
PS> $PSVersionTable
Name Value
---- -----
PSVersion 7.6.2
PSEdition Core
GitCommitId 7.6.2
OS macOS 14.8.7
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
No response
- Dominant language
- C#
- Stars
- 4.4k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PSReadLine
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSReadLine#5205 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PSReadLine#5195 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PowerShell/PSReadLine#5121 ·
-
Needs-Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
PowerShell/PSReadLine#5045 ·
-
Area-CommandHelp Issue-Enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
PowerShell/PSReadLine#3470 · 3 reactions ·
All issues in PowerShell/PSReadLine
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
azurenoops/spin_agent#975 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·