ctrl+h cannot work as same as backspace in MenuComplete

Open
#4,170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp, powershell
Domain
cli

Research direction

Reproduce with pwsh -noprofile, Emacs mode, ls -, and MenuComplete as described. Start at the MenuComplete handling for Ctrl+H and compare it with Backspace; done when Ctrl+H leaves ls - followed by the highlighted Path completion instead of producing ls -iteralPath.

Written by the indexing model from the issue text.

Description

Needs-Triage :mag:
Prerequisites
  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues, especially the pinned issues.
Exception report
N/A
Screenshot

image

Environment data
PS Version: 7.4.5
PS HostName: ConsoleHost (Windows Terminal)
PSReadLine Version: 2.3.5
PSReadLine EditMode: Emacs
OS: 10.0.19041.1 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 9001
Steps to reproduce

Run pwsh -noprofile for pure powershell start
Run Set-PSReadLineOption -BellStyle None -EditMode Emacs to bind emacs hotkeys, and ctrl+h can delete a character backward now.
Input ls - then press ctrl+space for MenuComplete, The Path is first completion so get highlighted
Press L and the LiteralPath is the possible completion, while the iteralPath is highlighted
Press ctrl+h

Expected behavior

Should be same as pressing backspace.
The actual command should be ls - and following a highlit Path

Actual behavior

The actual command becomes ls -iteralPath.
While the cursor is at character i.
It accepts the completion then delete a character backward.

Dominant language
C#
Stars
4.4k
Forks
341
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.