Re: another problem with failed import

[Edward K. Ream]

On Tue, Feb 4, 2020 at 4:25 PM 'tfer' via leo-editor <
leo-editor@googlegroups.com> wrote:

I wasn't aware that failed imports are supposed to block the save activated
> overwrite of the file for the @auto node, so I didn't pick up at first that
> that wasn't happening.  An @ignore directive was written to the body of the
> @auto node but saving the .leo file results in the node being written out
> anyway.
>

I doubt that. If so, it's a bug that should be fixed immediately.

@ignore does indeed suppress changes to an @auto x.js node.

> Thanks for you work Edward,
>

You're welcome.

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS2jBAh7-B9%2BtBWGOHCe%3D7s%2BP8nY%2B3Qh4F-NK08hvJiwRQ%40mail.gmail.com.

another problem with failed import

['tfer' via leo-editor]

I haven't had a chance to do my "by hand" rearrangement of reveal.js.  I'll 
look at how the improved importer does and incorporate that to get and 
outline for study.

I wasn't aware that failed imports are supposed to block the save activated 
overwrite of the file for the @auto node, so I didn't pick up at first that 
that wasn't happening.  An @ignore directive was written to the body of the 
@auto node but saving the .leo file results in the node being written out 
anyway.

Thanks for you work Edward,
  Tom

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/9165999b-68de-46e0-915f-546271054eb0%40googlegroups.com.