On Sat, 8 Jul 2017 08:46:07 -0500
"Edward K. Ream" wrote:
> On Sat, Jul 8, 2017 at 4:53 AM, vitalije wrote:
>
>
> > It seems that at-font settings kind is replaced with other methods
> > of configuration.
> >
>
> This is complicated. Iirc, the complications stem, in part, from the
> theme m
On Sat, 8 Jul 2017 00:57:14 -0700 (PDT)
vitalije wrote:
> I am confident that I can write command to open relevant
> settings file, make change there and save it again
Note that the Settings -> Edit Settings menu item machinery does some
of this. Well, really it's just copying settings from on
On Sat, Jul 8, 2017 at 4:02 AM, vitalije wrote:
> When user edits at-font settings node, clicking OK should adjust body of
>> node to selected font.
>>
>
> Done at 30c6dae.
> Warning: previously command show-fonts expected that font family is in
> clipboard and it copied selected font family in
On Sat, Jul 8, 2017 at 4:53 AM, vitalije wrote:
> It seems that at-font settings kind is replaced with other methods of
> configuration.
>
This is complicated. Iirc, the complications stem, in part, from the
theme machinery. @data qt-gui-plugin-style-sheet forms a "base" style,
which the use
While trying to test new show-fonts capabilities, I have noticed that in
leoSettings.leo there are just a few at-font settings. However, when
searching for at-font in Nav panel, it finds tons of settings of the
following form:
@string @font-...
It seems that at-font settings kind is replaced
>
> When user edits at-font settings node, clicking OK should adjust body of
> node to selected font.
>
Done at 30c6dae.
Warning: previously command show-fonts expected that font family is in
clipboard and it copied selected font family in clipboard after dialog
confirmation. Now this comman
