It's better not to make changes to the built-in themes, because they will get lost on the next Leo upgrade. You can instead put modified themes into your .leo/themes directory (create it if it doesn't exist). Leo will look there first so it will find and use your modified theme even if it has the same name as one that comes with Leo. That's what I do.
You'd be surprised at how well Leo can handle all kinds of things, but it's not always easy to discover them! For example, you may not know that Leo can highlight the current line in the body editor. See *Help/Open Help Topics/Help-For-Highlight-Current-Line*. On Thursday, October 30, 2025 at 11:55:31 AM UTC-4 [email protected] wrote: > Hi Thomas, > > Thank you to both you and Edward. I've persevered with Leo this > afternoon. The only thing I've done differently was keep the new settings > file inside the Leo folder, but I copied the font changes individually back > into the dark theme file. > I'm back working again and on 6.8.8 devel version. > > I did also check out LeoJS too. Think I prefer using the full application > for now. > > Many thanks. > > Kind regards, > Richard Twyning > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Thomas Passin <[email protected]> > Date: 30/10/2025 13:25 (GMT+00:00) > To: leo-editor <[email protected]> > Subject: Re: Upgrading Leo > > If you do keep using Leo itself (instead of LeoJS), two things. First, > it's not usual for the myLeoSettings.leo file to be replaced. It's > intended to hold all your custom settings. The base settings file, > LeoSettings.leo does get replaced but that has to happen, at least when > some feature of Leo changes. You should put any custom changes into your > myLeoSettings.leo file. and they won't get lost in the future. The > settings in myLeoSettings.leo will not get lost or replaced. Of course, if > you have a custom setting that has become obsolete, it won't take effect. > > Second, the code for creating the layout of Leo's panes has undergone a > drastic change and functions differently from the way it used to. I forget > when this change happened but it might be since you started using 6.8.2. > There is a Help item about using layouts. Open it with the "Help/Open > Help Topics/Help-For-Layouts" menu item. It shows all the layouts and says > how to set Leo to use any one of them > > On Thursday, October 30, 2025 at 8:38:40 AM UTC-4 Edward K. Ream wrote: > >> On Thu, Oct 30, 2025 at 5:17 AM Low Priority Services < >> [email protected]> wrote: >> >> No, I haven't yet. This is the first I've heard of it this morning. I >>> do use VS code on both Linux and Windows, so I'll definitely have a look at >>> it. >>> Thank you :-) >>> >> >> You're welcome. I imagine a plugin for vscode will be an easier sell to >> your people than some obscure app like Leo. Good luck! There is no way I >> can thank Félix enough for bringing Leo to vscode. >> >> Edward >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "leo-editor" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/FSGP0MGlXiI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/leo-editor/d894661f-4961-4355-83c3-1cae93dfd412n%40googlegroups.com > > <https://groups.google.com/d/msgid/leo-editor/d894661f-4961-4355-83c3-1cae93dfd412n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 visit https://groups.google.com/d/msgid/leo-editor/8a29dd0e-4aaa-417a-b446-40f2b8e13e86n%40googlegroups.com.
