When I study a program, I like to import it into Leo. I have several
scripts that do this: some create @auto nodes; others create @file
nodes.
Either way, the import process has the potential to change many
files. Usually, I just change @auto and @file to @@auto or @@file, so
that any changes I make while studying the code won't affect the
originals.
But this "safety first" approach means that I can't actually use Leo
to insert tracing statements (or for any other changes.) A few days
ago, I found a way to import "live" code into Leo safely:
Create a bzr repository for the code before importing it
The Aha is to create the repository *wherever the code is*, including,
say, python/Lib/site-packages.
- bzr qdiff ensures that import hasn't significantly altered the code,
- bzr revert undoes any unwise or unwanted changes.
This is exactly what I need: I can make changes to important tools
*safely* within Leo.
I often feel like I must be the last person in the world to have
gotten this Aha, but I'm happy with it anyway ;-)
Edward
--
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.
