You're right, themes seem to have been completely nerfed.
ekr_dark_theme has a @data node, but it doesn't seem to work.
At one point there was infrastructure to build the @data node from a
Leonine tree outline of the theme.
I'll try and have a look at it.
Cheers -Terry
On Tue, 13 Dec 2016 11:4
On Mon, 12 Dec 2016 10:56:28 -0800 (PST)
Curtis Carlsen wrote:
> I downloaded the new code base to try out the new importers. (Leo
> 5.4, december 8th)
>
> I am seeing extended stalling of different parts of the program,
> where everything freezes and the program does not respond to
> keypresse
I'm testing on the current master as of today and themes are not working as
advertised on Linux/Python3/PyQt4.
I can copy my old "theme" node headlined "leo_dark theme 0" from my daily
driver version of Leo to my test master and it will load fine.
The important node to this "theme" is headlined
I moved forward on this myself, at least the command line option part.
Please see pull request
here: https://github.com/leo-editor/leo-editor/pull/349.
On Tuesday, December 13, 2016 at 11:01:38 AM UTC-5, john lunzer wrote:
>
> In my explorations of Leo in trying to make Leo useful from the comma
In my explorations of Leo in trying to make Leo useful from the command
line I'm faced with the limitation that it seems that when opening a
non-.leo outline file from the command it's hard coded to open these files
as @edit nodes.
I am suggesting/requesting that an option be added to Leo to di
On Mon, Dec 12, 2016 at 2:50 PM, Largo84 wrote:
> No, the refresh from disk was for a @auto-md node. The ``@@`` was in a
> child node headline.
>
Thanks for the clarification.
The problem is likely the following regex:
md_hash_pattern = re.compile(r'^(#+)\s*(\w+)(.*)\n')
in the is_hash me
