-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Vesktop on macOS not working #698
Comments
I am not very familiar with our nix-darwin support. Do you have any idea why Kitty and VSCode are working, while Vesktop is not? For reference, here are the relevant guards:
The #400 tracking issue might be of interest. |
the only reason that i can think of for the vesktop target not working on macOS is the fact that it might not save its configuration data into whatever |
Perhaps if I import the .config/vesktop/themes/stylix.theme.css in the quick css in vestkop it will work but this seems like a rough solution I am away from my system right now so I can't even test the theory above |
Hey @itsvic-dev I've just ended up copy pasting the stylix.theme.css into the dedicated theme folder that version uses which is in Application Support but that's not very reproducible. If anyone has any ideas pls bring them forward |
I believe the Vesktop theme has to be manually enabled from Vesktop settings. (This sounds like a different issue but leaving this here in case its useful to anyone) |
Hey, @danth. It is not listed in the themes section of vesktop as the stylix.theme.css is not symlinking to the correct place on macOS |
@danth I think a simple fix is to check if the system is macos and change the symlink to ~/Library/Application\ Support/vesktop |
Is this not a general $ git checkout --quiet 51ad2cec11e7 && rg 'xdg\.configFile' | wc --lines
10 In that case, should not all these instances cause the same problem? |
Hey, @itsvic-dev @trueNAHO check out my pull request #784 |
Stylix works for everything besides Vesktop. Everything basically means kitty and vscode
The text was updated successfully, but these errors were encountered: