Skip to content

'Ctrl-C' and 'Ctrl-V' shortcuts do not works correctly with the terminal. #605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
LaurentDardenne opened this issue Mar 23, 2017 · 1 comment

Comments

@LaurentDardenne
Copy link

System Details

  • Operating system name and version: Windwos Seven Fr sp1
  • VS Code version: 1.10.2
  • PowerShell extension version: 0.11.0
  • Output from $PSVersionTable:
Name                           Value
----                           -----
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with 'Ctrl-C' and 'Ctrl-V' shortcuts and the terminal.

When i use F8 with this code inside the editor :

Get-ChildItem c:\temp|
 Where-Object {$_.FullName -match '\.txt'}|
 format-list -Property fullname

this works :

PS C:\temp> Get-ChildItem c:\temp|
 Where-Object {$_.FullName -match '.txt'}|
 format-list -Property fullname


FullName : C:\temp\log1.txt

FullName : C:\temp\log2.txt

FullName : C:\temp\script.txt

But when I use Ctrl-C and Ctrl-V, I get errors :

PS C:\temp> Get-ChildItem c:\temp|
An empty pipe element is not allowed.
At line:0 char:0
PS C:\temp>
PS C:\temp>  Where-Object {$_.FullName -match '.txt'}|
An empty pipe element is not allowed.
At line:0 char:0
PS C:\temp>
PS C:\temp>  format-list -Property fullname
@daviwil
Copy link
Contributor

daviwil commented Mar 23, 2017

Yep, this is because we're missing multi-line input support right now, follow this issue: #569. The plan is to fix this in the next feature update.

@daviwil daviwil closed this as completed Mar 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants