My apologies if resurrecting old threads is frowned upon here, if so let me know and I'll try to refrain in future. . .
> On Tue, Nov 8, 2011 at 9:49 AM, mdb <[email protected]> wrote: > > I vote for using rst2pdf > > Thanks for your vote. I'm leaning the same way. I think using > standard tools wherever possible is a big improvements over hacks like > leo_pdf.py. I'm also looking to build this type of toolchain: Leo as the container/ generator and meta-organizer for a tree of plaintext docs. I was thinking of Leo as just outputting the alternative select/sequencing paths of output, but now see that it can also manage the external tools that will be converting the single-source files to their target (in some case intermediate) filetypes. Although I'm no coder, Leo's tremendous value may spur me to dip my toes in that water with a bit of Python scripting if that becomes necessary, although I'm hoping to stick with batch files/bash scripts if at all possible. I assume the basics are doc'd on triggering such scripts and external CLI utility tools to run against individual files, so I'll ask the higher-value question: In the case where files are as likely to be modified outside of Leo as in, is there a way to have Leo check for their modified status in a whole branch of subdirs, triggering the external executable to run against any files that been modified? I'd rather not have to re- generate a whole tree when just a few files are getting changed at any time. Or alternatively, does anyone know of a generalized helper utility for this that would work outside of Leo to: - watch a dirstruc hierarchy - track the timestamps of the source files - run an arbitrary script/executable against and any new or changed files Could be windoze or linux, the file trees are getting sync'd around anyway via unison Thanks in advance. . . -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
