On Tue, Aug 27, 2019 at 8:25 AM vitalije <[email protected]> wrote:
> My point was that those additional required steps that I have to do to
fix my Leo are introduced just by updating Leo.
I do apologize for the problems you have been having. My intention is to
leave existing settings alone, wherever possible. I do retire newly unused
settings from leoSettings.leo.
Behavior such as you describe can legitimately be called a bug. The
general principle is new settings in leoSettings.leo should have default
values the preserve Leo's legacy operation.
> You probably have to make the body pane the central widget:
@string central-dock-widget = body
Probably, but it would again require more of my time to tweak
> myLeoSettings.leo having to reload it all the time. I might do this, but I
> prefer to wait until it is stabilized.
>
It should be stable as of Leo 6.0. The present work with global docks
should not affect you, because it is in the gui branch. Even when merged
into devel, global docks will only happen when --global-docks is in effect,
and even then there are, iirc, no new settings.
> My point is, you have many times introduced changes that required users to
>>> change their settings or to give up updating Leo.
>>>
>>
You are the first to complain of such serious settings problems. As I said
in my original reply, the goals of stability and innovation are inherently
somewhat at odds.
However, the principle of retaining legacy operation in the default
settings in leoSettings.leo should mitigate this tension.
I'm not sure why you have such problems with your settings. It should be
>> possible to fix them with Leo as it is.
>>
>
> I am not saying it is impossible. It just takes time and effort which I am
> not so eager to put into the tweaking my settings now.
>
Fair enough.
> If it was possible for me to change setting central-dock-widget with a
> menu or even through executing minibuffer command I would have tried this.
> If it was possible for me to change theme setting in the menu or executing
> minibuffer command I would have tried this.
>
It's called reload-settings. I think we both agree that it won't work.
> Maybe it takes just to add two headlines to my settings file, but I am not
> sure. In my experience it might just turn into an hours long session of
> fixing some visual issues. That is the reason I rather choose not to follow
> this path.
>
> The real issue here is not my configuration problems. I am more concerned
> with the other users especially new ones.
>
Let's let newbies speak for themselves.
I have just tested that reloading all settings won't change theme. You can
> say that is how it is supposed to work. But for me this is a bug.
>
Fair enough.
> If we just put aside question how Leo should handle settings for a moment.
> Telling user that it is impossible to change theme on the fly because it is
> technically impossible to achieve this is a bit awkward and false. The
> sizes, colors, and fonts can be easily changed and immediately visible in
> PyQt widgets. The fact that we, Leo developers, can't deliver that feature
> to the Leo users is something we should be ashamed of.
>
Ahem. If you think reload settings can update themes, feel free to do so.
It's a reasonable enhancement, that can be done without any major changes
to Leo's configuration machinery. You would most likely want to change (or
create) methods called reloadSettings or reload_settings (depending on the
class).
The reason why we can't deliver it lays in an inadequate way how Leo
> handles its own configuration.
>
No. It's an indication of the complexity of themes.
I think we are done discussing this topic.
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/CAMF8tS0kTwMD-i1A4iTWjUD97DxFbEEvMc1pAqizpcmYoYT6qw%40mail.gmail.com.
