-
Notifications
You must be signed in to change notification settings - Fork 6
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
Script fails under Windows 10 #7
Comments
Oh, and note that I had to hard-code the value of /mnt/c for USERPROFILE_MNT. It won't find that no matter what I try. That's why it shows up when I run it via sudo. |
Update: As per comments in this thread: |
Update: Re-installed Slack over top of my non-working install. |
The For me however, It still doesn't work. I still get the stock white backgrounds as if it won't load the DOM event at all. |
I ended up having to change This worked for me. I also mentioned this on https://github.com/widget-/slack-black-theme/issues/98 |
@kurtzberger confirmed. Adding the double backslash fixes the detection of folders. Looks like the script is now functional on my end. |
If you're using windows use this in powershell (running in Administrator mode):
Run this for a custom slack theme, just use this repo's theme. The raw link: https://raw.githubusercontent.com/earlduque/Slack-Dark-Theme/master/dark.css If you have issues, please visit here: https://github.com/benjamhooper/slack-custom-theme |
Not sure this is completely fixed. I just tried this and i'm getting a similar error returned when I try to run it under WSL (Ubuntu 18.04):
I'll add that there is no ssb-interop.bundle.js in the install tree for Slack 4.0.0 on Win 10 either. So unless this script is supposed to create it, I don't know how it gets there?
Update: I added a bunch of echo statements to try and diagnose why it's not finding things. That showed me that it wasn't populating the USERPROFILE_* variables, which meant it wasn't populating WIN_HOME properly or APP_VER, etc. etc. That's now fixed, but it still fails with a permission error:
If I run the same script as sudo ./darkSlack.sh, I get this instead:
The text was updated successfully, but these errors were encountered: