-
Notifications
You must be signed in to change notification settings - Fork 175
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
Not work on Windows 1803 #36
Comments
I can update link the following way successfully. |
Getting this error as well when trying to update Powershell Colors. Mine reads similar:
Going to investigate this more in the next day or two. Will post back here if I find anything |
I Assume this is because PSReadLine has been updated to version 2.0.0. I was not able to find enough documentation in my limited time to understand how to fix this script, but that seems like the necessary next step. https://www.powershellgallery.com/packages/PSReadLine/2.0.0-beta2 |
I ended reverting away from these tools entirely and using the Windows 10
colortool from
https://github.com/Microsoft/console/tree/master/tools/ColorTool instead.
It has solarized themes built in and is supported by MS directly so
hopefully won't get broken. I'm not sure the scheme is quite as accurate,
but it's good enough for me!
…On Tue, Sep 18, 2018 at 11:28 PM Thada Wangthammang < ***@***.***> wrote:
Firstly, I got error as same with you
PS C:\Users\mildronize\Desktop\cmd-colors-solarized-master> Get-ExecutionPolicy -List
Scope ExecutionPolicy
----- ---------------
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined+ CurrentUser RemoteSigned
LocalMachine Undefined
I think It depends on your ExecutionPolicy.
In my case, I use RemoteSigned on CurrentUser
So, I need to unblock all ps1 files that involves with this script
[image: powershell]
<https://user-images.githubusercontent.com/3647850/45727363-9d917900-bbed-11e8-9e63-1d4a9e03fc02.PNG>
Here is a file list that I already unblocked, (or other files you wish to
run on your computer)
Get-Link.ps1
Update-Link.ps1
Set-SolarizedDarkColorDefaults.ps1
Set-SolarizedLightColorDefaults.ps1
P.S. Update-Link.ps1 will call Get-Link.ps1. So, Get-Link.ps1 should have
a permission to run too
Or you can use other ExecutionPolicy for unblocking everything (I don't
recommend)
Here is my result
[image: 2]
<https://user-images.githubusercontent.com/3647850/45727495-2f00eb00-bbee-11e8-890a-14128c41a8dc.PNG>
And my Windows 10 Pro version is 1803
I hope it should be work for you too, have fun 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATpU7yei8znqOVVOjsjP3vPTEYKrITLVks5ucavNgaJpZM4T9CRz>
.
|
There's a lot changing with respect to how the Windows 10 console works. I think if you are using Windows 10, the colortool is probably the right approach. With the colortool, you can modify it so the colors match the same as what this project tried to. As I recall the colortool scheme is slightly different in some shades, but in some ways it might be an improvement. Long term, the approach used with these scripts probably won't work with the new Terminal as it (thankfully) applies schemes in a different way. I think colortool might still work with it. You can find a few builds that people have made to experiment with. This project will remain applicable to the classical conhost terminal and shells, such as running cmd or PowerShell today, but it will hopefully be retired as the primary terminal window most people use in the next few releases. If you haven't seen it yet, look for the YouTube video announcing it at Build. ColorTool is in a slightly different place now: https://github.com/microsoft/terminal/tree/master/src/tools/ColorTool |
I had similar issues. The issue seems to be that the PSReadLine module doesn't like any changes to the properties of a shortcut via the Get-Link script It would be very bad if they moved to the colortool, because it does not provide all the features of the the old Get-Link script. As for the new Terminal,... we will see when it comes. Anyways, the solution is to downgrade the PSReadLine module to version 1.2. The 2.0.0-beta versions that ship with Windows 10 are really causing lots of issues and are far from stable. Have a look here for detailed instructions: https://github.com/stefaanc/psconsole#the-colors-of-the-console |
After upgrade from Windows 1709 to 1803, the Ubuntu bash reverted to the original colors. So I run
Update-Link.cmd C:\Windows\System32\bash.exe light
again.But it gave me the following errors.
The text was updated successfully, but these errors were encountered: