On Sun, Dec 13, 2020 at 12:51 PM poseidon <[email protected]> wrote: > Thank you, Edward! >
You're welcome. I'm glad you found a solution. Well, after playing around I found out that replacing DefaultTheme by None > in my settings did the trick. This means, that themes change font settings > and the like, too. Checked that by inspecting themes files (e.g. > EKRLight.leo). Makes sense, but then, why having those settings in > myLeoSettings as well? This makes the whole config'ing of Leo rather > complex, doesn't it? > Too complex :-) There are several reasons for the complexity: - Power: Leo allows per-file (.leo file) settings. - History: Themes were a late graft on existing settings. - Qt: Qt settings are a mishmash of style-sheets and programmatic options. So now we're kinda stuck. Nobody wants to change leoSettings.leo unnecessarily. Once things work, all of us, including you, just want to move on ;-) Would I change things if I were designing settings from scratch? Maybe, but that's a moot point. I do know that Félix's Leo plugin for vs-code will use vs-code's settings machinery. That's perfectly appropriate. Settings files are not the heart of Leo. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS1KiaK4tAgY%3DJ9u%2Bf_v%2BniFQpHrtmSv83bhkO5KLf6%2BNQ%40mail.gmail.com.
