On Fri, Apr 27, 2018 at 9:56 AM, Rob wrote:
> I restarted Leo w/ --no-cache option and I still get the error.
>
Thanks.
Looks like you have just uncovered a new markdown bug.
md.find_parent is tricky. A new guard might be all that is required, but I
would like to dig
I restarted Leo w/ --no-cache option and I still get the error.
Rob...
On Friday, April 27, 2018 at 10:08:52 AM UTC-4, Edward K. Ream wrote:
>
>
> Have you tried loading Leo with --no-cache? If that works, please clear
> all the caches and try again.
>
> Edward
>
--
You received this
On Fri, Apr 27, 2018 at 9:08 AM, Edward K. Ream wrote:
On Fri, Apr 27, 2018 at 9:05 AM, Edward K. Ream wrote:
>
>> On Fri, Apr 27, 2018 at 8:17 AM, Rob wrote:
>>
>> As usual, I update my Leo instance every few days or so (devel
On Fri, Apr 27, 2018 at 9:05 AM, Edward K. Ream wrote:
> On Fri, Apr 27, 2018 at 8:17 AM, Rob wrote:
>
> As usual, I update my Leo instance every few days or so (devel branch ).
>> After today's update and opening my standard set of files, I get this
On Fri, Apr 27, 2018 at 8:17 AM, Rob wrote:
As usual, I update my Leo instance every few days or so (devel branch ).
> After today's update and opening my standard set of files, I get this error:
>
Strange. Git reports that the last change to
plugins/importers/markdown.py
As usual, I update my Leo instance every few days or so (devel branch ).
After today's update and opening my standard set of files, I get this error:
reading: @auto-md Software.md
Exception running Markdown_Importer
Traceback (most recent call last):
File "D:\Synced\github repos\leo\leo
On Tue, Dec 13, 2016 at 7:25 AM, Edward K. Ream wrote:
>
The problem is likely the following regex:
[snip]
Fixed, I think, at rev bd90f4d.
As noted in the checkin log, actual @auto-md files import @@section names
correctly, but some dashed problem with the unit
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 =
No, the refresh from disk was for a @auto-md node. The ``@@`` was in a
child node headline. Sorry if that wasn't clear.
Rob..
On Monday, December 12, 2016 at 10:04:53 AM UTC-5, Edward K. Ream wrote:
>
>
>
> On Fri, Dec 9, 2016 at 12:41 PM, Largo84
> wrote:
>
>> Terry, I
On Fri, Dec 9, 2016 at 12:41 PM, Largo84 wrote:
> Terry, I added an addendum to my original post that I think indicates what
> caused the problem, the use of ``@@`` in the node headline. Not sure if
> that's a bug or a feature:-)
>
When I awoke this morning I thought of
Try this for yourself and see what happens:
Scenario 1 (@@ Section as first child node)
1) Create a new new empty node say, @auto-md Some File.md
2) Create a new child node say, @@ Section 1 (body text optional)
3) Save the file to create the external file. Viewed in external editor,
the layout
On Fri, Dec 9, 2016 at 12:41 PM, Largo84 wrote:
> Terry, I added an addendum to my original post that I think indicates what
> caused the problem, the use of ``@@`` in the node headline. Not sure if
> that's a bug or a feature:-)
>
>
Greetings from Northern Mississippi :-)
Terry, I added an addendum to my original post that I think indicates what
caused the problem, the use of ``@@`` in the node headline. Not sure if
that's a bug or a feature:-)
Rob..
> so you must be using a construct that I'm not using.
>
> Cheers -Terry
>
>
be using a construct that I'm not using.
Cheers -Terry
From: Largo84 <larg...@gmail.com>
To: leo-editor <leo-editor@googlegroups.com>
Sent: Friday, December 9, 2016 8:11 AM
Subject: Exception running Markdown_Importer
Just got this one this morning on one file:
Excep
Just got this one this morning on one file:
Exception running Markdown_Importer
Traceback (most recent call last):
File "D:\Synced\github repos\leo\leo\core\leoImport.py", line 915, in
scanner_for_at_auto_cb
return scanner.run(s, parent, prepass=prepass)
File "D:\Synced\g
15 matches
Mail list logo