Re: New Themes

On Tue, Aug 20, 2019 at 3:00 PM Matt Wilkie wrote: > Blue sky: I'd like to be able to run `show-settings` into a Leo panel, >> that has a filter category buttons plus a text field at top. From there I >> could 2x-click or [enter] on any given setting and be taken to the location >> where that is

Re: New Themes

> > Blue sky: I'd like to be able to run `show-settings` into a Leo panel, > that has a filter category buttons plus a text field at top. From there I > could 2x-click or [enter] on any given setting and be taken to the location > where that is currently defined (LeoSettings, myLeoSettings, >

Re: New Themes

> > I have always thought it rather puzzling to have self-contained themes and > then an entirely different way to set fonts. > My preference is to set everything related to UI in the theme. > I agree, all UI elements should be in one place. However people shouldn't have to wade through tons

Re: ENB: re singleton docks

> > I am considering switching to g.app.db for sizing Leo. That is, Leo's > main window would open with the size it happened when it last closed, > *regardless* of what outlines are being opened. Imo, this would be more > intuitive for users. This would also remove some

Re: New Themes

There is the Ctrl-+/- / Ctrl-mousewheel font zoom functionality to consider. I don't think it was incompatible with themes, it just required specific naming conventions... maybe, I don't remember the details. Anyway, just pointing out that factor's in there to be considered. Cheers -Terry On

Re: New Themes

It looks like the themes are supplanting font info but not anything else. For example, if I specify a setting in a theme file it gets overridden by myLeoSettings.leo which is the expected behaviour. Having the font info in a theme override that is inconsistent but could/should be offered as a

Re: New Themes

On Tue, Aug 20, 2019 at 8:32 AM Matt Wilkie wrote: > A structural problem: theme font-size overrides myLeoSettings.leo, which I > assume applies for all settings. I expect myLeoSettings to always have the > last say. > Hmm. I'm not sure what I expect. Edward -- You received this message

Re: New Themes

A structural problem: theme font-size overrides myLeoSettings.leo, which I assume applies for all settings. I expect myLeoSettings to always have the last say. Oh that's interesting, the `show-settings` command does not report base font settings, e.g. @font-size, @medium-font-size, etc.

Re: Having trouble writing a simple grouped undo/redo

On Tue, Aug 20, 2019 at 6:22 AM Brian Theado wrote: Unfortunately, I'm not able to run unit tests without getting a segfault. > Alright. Create a new branch, and I'll run the unit tests there. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor"

ENB: re singleton docks

This post contains a few notes in my Engineering Notebook. Feel free to ignore. *Rationale* #1289 : Singleton docks, is a precondition for using pyzo's features in Leo. Imo, #1289 is worthwhile all by itself. Leo's legacy operation is a

Re: Having trouble writing a simple grouped undo/redo

Unfortunately, I'm not able to run unit tests without getting a segfault. It appears to be related to loading the readline library similar to what I reported last year: https://groups.google.com/d/msg/leo-editor/ghiIN7irzY0/2wreFgcYDQAJ. Though now I'm running Ubuntu 18.04. Something in the unit

Re: Having trouble writing a simple grouped undo/redo

On Mon, Aug 19, 2019 at 7:04 PM Brian Theado wrote: > I found a core function which uses undo groups and used this code to call > it: > > c.createNodeHierarchy(['a', 'b', 'c'], parent=p) > c.redraw(p) > > Redoing this operation gives the same error as the test code and the > bead+1 fixes it

Re: enable theme file

在 2019年8月19日星期一 UTC+7下午7:16:31，vitalije写道： > > myLeoSettings.leo file should be in ~/.leo/ folder. not in ~/ (your home > folder). > > and the setting you should have under the @settings node is: > @string theme-name=BreezeDark2Theme.leo > > thanks Vitalije.. it's solved. Vitalije > > On