On Tue, Apr 19, 2016 at 9:23 AM, 'Terry Brown' via leo-editor <
[email protected]> wrote:
[
>
> @string initial_split_orientation = horizontal bug]
> might be older than you think.
Thanks for these investigations. Caching is great, except when it causes
no end of troubles :-)
I feel like Alice in Wonderland, running as hard as I can to stay in one
place. Hehe. Ah well, there is no great need to release 5.3-b1 this week.
Much more important to fix everything.
As soon as you save a layout using
>
> free_layout that becomes the persistent layout for that outline (based
>
> on the path, as with other things in c.db).
What commands save this data?
> So if there is a saved
>
> layout, which would be the recommended way of setting initial
>
> appearance, initial_split_orientation should be ignored.
> c.db.get('_ns_layout') will tell you if there is a saved layout.
>
Big sigh. The startup code, including settings, is pretty mind-boggling.
Maybe we should just retire @string initial_split_orientation??? But that
seems a bit extreme for those who never use layouts.
a) there's a bug in c.db, when you create and save a new file, c.db
> in that file gives a key error
>
Is it reasonable simply to catch that error and ignore it?
b) when your new file's called ~/r/test.leo (~/r is a RAM disk I use
> for temp things) it remembers the saved layout name from a previous
> ~/r/test.leo, but ~/r/notthattest.leo worked as expected, i.e.
> c.db.get('_ns_layout') == None
>
I don't understand. Yes, the two "test" files aren't the same, but how is
the cache to know that?
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
