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 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/d894661f-4961-4355-83c3-1cae93dfd412n%40googlegroups.com.
