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
How to change colorscheme? #6
Comments
You need to select a new scheme, installing them makes them available, but Geany cannot (yet) read your mind to select which one you want. |
Are there instructions on your project homepage I'm not seeing? I can't see anywhere how to select a scheme. There doesn't appear to be a setting in Preferences - Interface. Is it something I need to do to the files manually in my OS? |
Menu->View->Change Colour Scheme... See here |
Ohhhh, thanks. |
There's only Default and Alternate to choose from. What is it with the version numbers ? My Geany says it's 1.26 Edit: My fault. I've renamed the top directory to colorschemes. I found colorschemes and filedefs in that and moved them up. Now there's some themes to pick. Sorry, |
I also struggled to figure out that you have to move them up in the directory. Could you add this to the readme for Ubuntu installation?
|
@janjackson the README already says:
And choosing the colour scheme is already in the Geany manual as I linked in my previous post. |
@janjackson I updated the README file in 4598c9f, hopefully it's a little more clear now. |
I installed Geany 1.37.1 flatpack on pop_os. I copied first manually, then using the |
@gabrielnemeth thats a problem with flatpacks. The Geany project does not make the flatpack, you should raise the problem with your OS. |
I followed the instructions on the homepage exactly, but my colorscheme hasn't changed when I restart Geany. Are there missing instructions?
"Extract the tarball and copy all of the files in the colorschemes directory to your C:\Users\YourUserName\AppData\Roaming\geany\colorschemes directory. Create this directory if it doesn't already exist."
The text was updated successfully, but these errors were encountered: