Did you know that you can enable VT100 terminal emulation in PowerShell as well as the Cmd window?
This will allow you to do adb shell to your Android device, and allows you to run “full screen” vi editing on any text file on the device.
Did you know that you can enable VT100 terminal emulation in PowerShell as well as the Cmd window?
This will allow you to do adb shell to your Android device, and allows you to run “full screen” vi editing on any text file on the device.
You must log in to post a comment.
I knew you needed tools for this in the past, but was not aware that somewhere in the Windows 10 release sequence this became supported, but is turned off by default.
Thanks for the URL teaching me that final bit!
It certainly is very handy!
Jeroen Wiert Pluimers You might like this little powershell snippet too?
Get-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer
Which PowerShell version does that need?
On a Windows 8.1 Pro edition:
PS C:bin> $PSVersionTable.PSVersion
Major Minor Build Revision
—– —– —–
——4 0 -1 -1
PS C:bin> Get-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer
Get-ComputerInfo : The term ‘Get-ComputerInfo’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstract …
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-ComputerInfo:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
I’m on Windows 10 1706
Lars Fosdal that’s one of the powershell things: windows < 10 does not update it to recent versions and there are huge differences between versions