Bug 451600 - Kate doesn't save "Color Theme" under "Settings"
Summary: Kate doesn't save "Color Theme" under "Settings"
Status: RESOLVED DUPLICATE of bug 447532
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: 21.12.3
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-17 03:31 UTC by RenanMDP
Modified: 2022-03-23 23:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RenanMDP 2022-03-17 03:31:34 UTC
• I'm on Windows 11.

• Kate version 21.12.3.

• Basically, the "Color Theme" under "Settings" is never saved.

• It does work if I go to "Configure Kate..." and switch the option for "Default theme for kate:". However, the Breeze Dark theme there doesn't correspond to the one under "Settings" and only darkens the text screen and not the whole editor.

• Any other configuration is being saved(I disabled the minimap and switched the language successfully).

Here's a video demonstrating the issue:

https://youtu.be/2hcHqPVaOiI
Comment 1 Nicolas Fella 2022-03-17 13:19:02 UTC
> Basically, the "Color Theme" under "Settings" is never saved.

Yes, that is broken. https://invent.kde.org/utilities/kate/-/merge_requests/668 works toward fixing that

> However, the Breeze Dark theme there doesn't correspond to the one under "Settings" and only darkens the text screen and not the whole editor.

That's sort of intentional. Settings > Color Scheme is the application-wide color scheme, the other is the editor color scheme, both have Breeze/Breeze Dark, and setting the app-wide scheme also sets the editor scheme, but there are other edit schemes that are not available as app-wide schemes. Unfortunately this is not very clear in the UI
Comment 2 Nicolas Fella 2022-03-23 23:05:13 UTC

*** This bug has been marked as a duplicate of bug 447532 ***