Yes, that is what I thought. The best bet is for me to write a script that would copy the @file output to another file, say filename_head.py, and then it just trims the #@ entries I don't want in that new filename_head.py. I could even attach the script to an @file write trigger (I suppose that exists!) if I wanted to have that extra file generated automatically.
Thanks for the suggestions and clarifications! Bill Le dimanche 13 octobre 2013 12:51:29 UTC-7, Jacob Peck a écrit : > > On 10/13/2013 3:10 PM, wgw wrote: > > In short, can the user create a new file output directives (to go > > along with @file, @auto, @nosent, etc) ? > From my quick jaunt into the source... not without hacking on Leo's core. > > You could write a script that would save a file in a particular format > though, sourcing it's contents from the nodes. This wouldn't be > trivial, and would likely involve looking into the sources. > > -->Jake > -- 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/groups/opt_out.
