environment:
Windows 10 + PowerShell 5.1/7.2 (either)
Suppose you created a folder called D:\work\■test that contains a "black square."
Copy (Ctl+C) the string from this folder to the clipboard and paste it directly into the PowerShell console to leave the ■ character missing.
However, if you go through the Clipboard History feature (Ctl+V) in Windows, you will be able to complete the pasting without any missing parts.
Q1. Am I correct in understanding that the character code maintained in Clipboard Copy (Ctl+C) is different from the character code stored in Clipboard History function?
Q2. Please let me know if there is a way to stick ■ to the PowerShell console without missing it through the clipboard history function.
This is not an urgent question, but I was not satisfied with this action, so I asked you a question.
windows-10 powershell
Q2. Please let me know if there is a way to attach ■ to the PowerShell console without missing it without going through the clipboard history function.
Ctrlv should work.私 It worked well in my environment.
It seems that this phenomenon occurs when you right-click it.
It's a different solution.Checked the PowerShell Properties (optional) Legacy Console and re-launched PowerShell to eliminate this symptom.
Q1.
Am I correct in understanding that the character code maintained in Clipboard Copy (Ctl+C) is different from the character code stored in Clipboard History Feature?
I think it's a bug in Powershell's console(?) (a bug in pasting).The content of the clipboard is the same, and right-click paste has a problem, and Ctrlv does not cause the problem, so I don't think the content of the clipboard is the cause.
© 2024 OneMinuteCode. All rights reserved.