@LarsGit223 The thing is that *~/.config/gtk-3.0/gtk.css* has the highest
priority possible -- user priority. It's actually pretty much the right thing
to do to let this win.
In our specific case where it's a user setting, it could be arguable that we
should give it user priority, and then it *might* work, although I'm not
confident our dynamic style would overwrite anything in
*~/.config/gtk-3.0/gtk.css*, unless we give it higher priority, which we
probably shouldn't as it wouldn't be semantic.
All in all, I'm not even sure the behavior described in this report is wrong.
After all, the user selected a specific font in a place meant to override
*everything*, so why would we fight it? If the user really wants something
else, it's totally possible to have the right piece of CSS in
*~/.config/gtk-3.0/gtk.css* to do so, likely something like this:
```CSS
#GeanyMainWindow paned>paned:first-child>notebook:first-child
scrolledwindow:first-child>treeview { font: sans 12; }
#GeanyMainWindow paned>notebook:last-child scrolledwindow>treeview { font:
monospace 14; }
```
We could possibly make this easier by giving a CSS ID to the symbols pane's
treeview if really needed, but again the only case it matters is when this gets
overridden manually.
In the end, yes, providing a custom `GtkCssProvider` might work, but the
priority might have to be > to `GTK_STYLE_PRIORITY_USER`, which doesn't
necessarily seem like a good idea. And I'm not sure it's worth the trouble
going through all this just for a corner case that already has a workaround.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2069#issuecomment-513962621
