Word selection currently is rather coarse – It should be configurable what characters are considered "word boundary" #26518
Replies: 4 comments
-
|
This applies to the PSReadline module. You can configure it using $ (Get-PSReadLineOption).WordDelimiters
;:,.[]{}()/\|!?^&*-=+'"–—― |
Beta Was this translation helpful? Give feedback.
-
|
I don't quite understand: How do these delimiters fit the above example where the selection switches between Temp... and File '.\Temp...? Shouldn't they rather switch from Temp... to \Temp..., then .\Temp... etc.? |
Beta Was this translation helpful? Give feedback.
-
At first I thought you were unhappy with the word separators. The word is selected up to the next delimiter, depending on the direction of selection, the previous delimiter is included in it.. This is how I understand the selection algorithm. Write them issue, their repo is not belong this one. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I see. I created PowerShell/PSReadLine#5023 now. Thanks for pointing me! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, editing and selecting text, like expressions or file paths, in the PowerShell REPL is quite cumbersome because only letters (Regex
\wcharacter group) are considered word boundaries:I suggest to add additional logic to the PowerShell REPL so that selecting bulks of text will become easier to handle.
Beta Was this translation helpful? Give feedback.
All reactions