Re: Theme Problems

2016-12-13 Thread 'Terry Brown' via leo-editor 
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:48:32 -0800 (PST)
john lunzer  wrote:

> 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 @data 
> qt-gui-plugin-style-sheet, without that the theme does nothing.
> 
> In the current master the "reload-styles" command appears to do
> nothing, it doesn't generate the @data node.
> 
> It is interesting is that a great deal of the detail in the current
> master "leo_dark theme 0" seems to be missing compared to what I
> copied years ago. There used to be an "@button reload-styles" node
> contained in these themes which *does* successfully generate the
> needed @data node.
> 
> Themes used to work and it looks like there was possibly an attempt
> to simplify them and in the process now they don't work.
> 
> I would argue that themes are critical to overall Leo adoption and as
> long as this sits broken we risk losing new users.
> 
> On Tuesday, May 17, 2016 at 2:55:17 PM UTC-4, Edward K. Ream wrote:
> >
> > On Tue, May 17, 2016 at 1:33 PM, Mike Busch  > > wrote:
> >  
> >> I was able to get bg and fg colors to change with the Appearance 
> >> settings. As far as I can tell, Theme isn't read/used.
> >>  
> >
> > ​Good.  I do think your idea for a theme plugin would be useful.
> >
> > 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: leo stalling for long periods

2016-12-13 Thread 'Terry Brown' via leo-editor 
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
> keypresses or mouse clicks.  The stall lasts for up to 30 seconds or
> a minute, then things start working again.  It seems to happen at
> random intervals.  I don't have to be doing anything, sometimes I am
> just looking at a node, or navigating the tree and it freezes.
> 
> I have seen it happen when editting nodes, and also when I am in the 
> file|import any menu item.  It doesn't really seem to matter what I
> am doing at the time.  And if I run leo from the terminal, I don't
> see any error messages there.  The file I am editting is fairly large
> (1.15 MBytes)

Hi Curtis,

Are you editing the whole 1.15 MBytes in a single node?  I think Leo
would struggle with that.  If not, then I'm not sure what might be
causing your problem.

If you do have everything in one node, you can probably break it up
with a layout like:

   @clean myfile.dat
"@others"
 node1
"text for node 1"
 node2
"text for node 2"
 node3
"text for node 3"

where the top node would literally just be "@others", but the other
nodes would be much larger chunks of text.

> I am running on Windows 7, python 2.7
> 
> If I revert to using leo 5.1 final from October 20th, the problem
> goes away.

Hmm, so it works in an earlier Leo... I guess we need a more detailed
description of what you're editing - if you could share the file that
would help.

Cheers -Terry

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Theme Problems

2016-12-13 Thread john lunzer 
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 @data 
qt-gui-plugin-style-sheet, without that the theme does nothing.

In the current master the "reload-styles" command appears to do nothing, it 
doesn't generate the @data node.

It is interesting is that a great deal of the detail in the current master 
"leo_dark theme 0" seems to be missing compared to what I copied years ago. 
There used to be an "@button reload-styles" node contained in these themes 
which *does* successfully generate the needed @data node.

Themes used to work and it looks like there was possibly an attempt to 
simplify them and in the process now they don't work.

I would argue that themes are critical to overall Leo adoption and as long 
as this sits broken we risk losing new users.

On Tuesday, May 17, 2016 at 2:55:17 PM UTC-4, Edward K. Ream wrote:
>
> On Tue, May 17, 2016 at 1:33 PM, Mike Busch  > wrote:
>
>> I was able to get bg and fg colors to change with the Appearance 
>> settings. As far as I can tell, Theme isn't read/used.
>>
>
> ​Good.  I do think your idea for a theme plugin would be useful.
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Option to determine which @ directive to use when opening non-.leo files from the command line

2016-12-13 Thread john lunzer 
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 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 dictate which 
> @ directive to use when opening these non-.leo files. It could be 
> either an option at the command line or added to the Leo settings. Or both, 
> and the command line option would override the Leo settings.
>
> I find it strange that an @edit node is the default. If a user is opening 
> a file in Leo I'm inclined to believe they wanted to use Leo's parsers. If 
> they wanted an @edit they could just open the file in vim or other line 
> editor. 
>

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Option to determine which @ directive to use when opening non-.leo files from the command line

2016-12-13 Thread john lunzer 
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 dictate which 
@ directive to use when opening these non-.leo files. It could be 
either an option at the command line or added to the Leo settings. Or both, 
and the command line option would override the Leo settings.

I find it strange that an @edit node is the default. If a user is opening a 
file in Leo I'm inclined to believe they wanted to use Leo's parsers. If 
they wanted an @edit they could just open the file in vim or other line 
editor. 

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Exception running Markdown_Importer

2016-12-13 Thread Edward K. Ream 
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 method. It requires a *word *following 1 or more '#'
characters.  That's too strict, it seems.  Instead, it should just eat
everything except trailing whitespace.

Playing around with pythex , it appears that the
following might work:

md_hash_pattern = re.compile(r'^(#+)\s*(.+)\s*\n')

You can try this yourself if you like.  I probably won't get to it today.

EKR

-- 
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.