The ability to copy part of the output of the previous command to the current command
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by narrowing whether the feature should use interactive selection, command syntax, or an editor, then identify the relevant PSReadLine surface and define expected behavior for the examples. Done should include an agreed interaction model and tests covering selection from prior output.
Written by the indexing model from the issue text.
Description
Prerequisites
- Write a descriptive title.
Description of the new feature/enhancement
This is not a feature request that has a clear description and expectation, but more of a big general idea.
I often find myself need to grab a text from the output of the previous command and put it in the current command that is under compose. Using the mouse to select the text, copy and paste it into the current command does the job, but is inefficient.
Technically you can run the previous command and pipe it to a text editor and copy the text. However the point is that the need of copying part of the previous output is usually emergent, meaning you do not know that you need to do it until you are in the middle of composing the current command. As a workaround, you may perform some magic to always capture command output in a file and when needed, get the text from that file. However, with that, it is still requires additional steps and is not very neat.
There should be a way to:
- Interactively select and copy (or some other mechanism that does not neccessarily require clipboard) a text from the previous output (right in the terminal?)
- Or a command with text-selection syntax, e.g
ssh $(2,3)(the third text from the second line of the previous output), which will resolve to the expected text when executed - Or open text editor with the content being the previous output, from which you can choose the text
- etc.
A few examples that show how useful it is to be able to quickly grab some text from the previous output and put it in the current command:
> build
...
Error: syntax error in file 'foo/bar/baz.cpp'
> code foo/bar/baz.cpp
> health-check
...
Error: connection refused. IP: 208.232.96.166
> ping 208.232.96.166
> git status
modified: foo.txt
> git diff foo.txt
> Get-Content ./file.txt
One two three
four five six
> Set-ClipBoard -Value 'five'
Proposed technical implementation details (optional)
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 ·