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 > @<file> 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.
