another problem with failed import

16 views
Skip to first unread message

tfer

unread,
Feb 4, 2020, 5:24:58 PM2/4/20
to 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

Edward K. Ream

unread,
Feb 5, 2020, 4:05:16 AM2/5/20
to leo-editor
On Tue, Feb 4, 2020 at 4:25 PM 'tfer' via leo-editor <leo-e...@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
Reply all
Reply to author
Forward
0 new messages