Word selection is too coarse, doesn't stop at non-letter characters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start in the PSReadLine PowerShell REPL handling for CTRL+LEFT/RIGHT and CTRL+SHIFT+LEFT/RIGHT word movement. Reproduce the provided Out-File '.\Temp\Test.csv' example and verify that navigation and selection stop at each non-letter boundary shown in the expected behavior.
Written by the indexing model from the issue text.
Description
Currently, editing and selecting text, like expressions or file paths, in the PowerShell REPL is quite cumbersome because only letters (Regex \w character group) are considered word boundaries.
I would expect the cursor to stop at the next non-letter (Regex \W character group) character when navigating using CTRL + LEFT/RIGHT ARROW.
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.
Screenshot
Environment data
PS Version: 7.5.4
PS HostName: ConsoleHost
PSReadLine Version: 2.3.6
PSReadLine EditMode: Windows
OS: 10.0.19041.4406 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 9001
Steps to reproduce
- Enter a text like the one from the screenshot into a PowerShell window:
Out-File '.\Temp\Test.csv' - Move the cursor using CTRL + LEFT/RIGHT ARROW keys
Expected behavior
Pressing CTRL + SHIFT + LEFT/RIGHT ARROW keys, I'd expect text selection to switch from Temp... to \Temp..., then .\Temp..., '.\Temp..., File '.\Temp... etc.
Actual behavior
Pressing CTRL + SHIFT + LEFT/RIGHT ARROW keys, text selection switches from Temp... to File '.\Temp... etc.
- 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 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·