I'll comment on my own issues as I've been trying to work through them. 1. I went in to the code and poked around to see what was going on. It seems that 'bash' isn't in the self.extension_dict in the leoApp.py file. This is why my bash scripts weren't being set to @language shell. 2. This is not strictly necessary I suppose, I can just set a keyboard shortcut to refresh-from-disk.
One of these days I need to get around to figuring out how to add a pull request to git... On Saturday, March 21, 2015 at 1:52:16 PM UTC-4, john lunzer wrote: > > Thanks, I think I'm part of the way there, @edit is sort of working. > > Two issues: > > 1. It keeps adding @nocolor to the beginning of the @edit node body, there > was no @nocolor anywhere in the @clean outline node. Is there a way to get > it to stop adding this directive? > > 2. Is there a way to trigger a Refresh From Disk automatically after a > save (Ctrl + S)? > > > Between those two issues it's more cumbersome to use Leo for reviewing > flat files than an external editor. > > > > > On Saturday, March 21, 2015 at 1:32:12 PM UTC-4, Edward K. Ream wrote: >> >> On Sat, Mar 21, 2015 at 12:11 PM, john lunzer <[email protected]> wrote: >> >> What I would like is a node with the same filename as my @file/@clean >>> outline node that simply contains and* up to date flat view* of my >>> @file/@clean outline node. >>> >> >> As you say, just use @edit, and then refresh-from-disk to see the up-to >> date code. >> >> The @edit node won't be marked dirty unless you mess with it, so it >> should be relatively safe, especially if it comes before the @clean node in >> the outline. >> >> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
