On Feb 19, 6:34 am, Kent Tenney <[email protected]> wrote: > I thought being on the command line would signal that the file was > a Leo file, but evidently Leo can be passed any filename, will put > it into an @edit node. I just tried > $ leo myfile.py > > and see that Leo puts the .py file into an @edit node, doesn't parse it.
Yes. Iirc, you requested this feature ;-) > If Leo does the same thing always with filenames in argv, assuming > a Leo file might be acceptable. It's not clear *exactly* what Leo should do when loading files, which is why nothing can be done now. There are several complications: 1. Leo can sometimes put files directly into @edit nodes. 2. Leo can sometimes read zipped Leo files. I'm not sure whether this depends on the file extension. I think it does, but don't remember for sure. 3. When writing an outline, Leo will ensure a .leo extension, but probably not for zipped outlines. I actually would prefer to leave the code as it is. If you want Leo to load a .leo file, I don't think it's too unreasonable to expect a .leo extension. 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.
