-
Notifications
You must be signed in to change notification settings - Fork 11
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
Readme on how to use with helix #13
Comments
If you don't mind using the Catppuccin theme [1] (specifically, th Mocha and Latte variants), then you can change your Helix config to be like my config [2]. If you'd like to use your own themes, you'd need to edit the source code! Otherwise, no specific set-up is needed. [1] https://github.com/catppuccin/helix |
Updated the README [1]. :) [1] https://github.com/jesse-c/AppearanceNotifier/commits/main/ |
Thanks so much! Yeah, this will be enough to get me going. ((long parenthetical) though i'll re-visit it when i properly set up the helix theme to my liking. I'll need to port over my modestly customized vscode versions of base16/tomorrow themes (which i've recently coined as tuesday (light) and thursday (dark))) Unfortunately, Catppuccin is too blue-colored for my taste, not good for my poor eyes. So far, with my light use of helix, i've just used base16_transparent modified to work better with my iterm config with a light/dark AutoLaunch python script, so with the transparent theme, it just uses the terminal colors already, the colors switch, but i'm missing a couple extra customizations. |
I agree re: Catppuccin being a little too blue. Those 2 variants I use I find to be the most bearable. I at the moment wouldn't dare attempt to customse it or make a new theme, since there's themes for almost every app, for Catppuccin. 😅 I had no idea that iTerm had the kind of functionality, so it's interesting to see. |
It would be great to have some info on how to set up helix to use with this! (Found via your comment here)
The text was updated successfully, but these errors were encountered: