b4n left a comment (geany/geany#4326)
> But if we specify some different value there, it will get overridden by
> geany's css.
Bummer, yeah we don't have priority FALLBACK⋅ not sure why we don't, but I
remember this was messy. So yeah we'd override the theme -- unless maybe we're
lucky and a theme doing something like `#GeanyDialogSearch entry.monospace {
font-family: Consolas, monospace; }` wins over a *geany.css* containing
`.monospace { font-family: monospace; }`. Unless we can really depend on
themes properly defining the `monospace` style class, but that might be a bit
unrealistic :unicorn:
> Or, actually, since it's possible to set the font for the messages window, it
> should also be possible to set it for the entry in the search window, right?
> I haven't checked the code so I don't know how exactly this works. We could
> maybe reuse the settings e.g. for the messages window - it probably doesn't
> make sense to have a separate settings for such a small thing. We should just
> not set the font size (if such a thing is possible).
We use `ui_widget_modify_font_from_string()` which currently uses deprecated
features internally. The current "right way" is to inject some CSS, which can
also be done. But that function still works, though, so yeah it could be a
solution.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4326#issuecomment-2957228741
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4326/[email protected]>
