great, tested it that way, amazing stuff, thanks. On Tuesday, June 25, 2013 10:38:41 PM UTC+2, Matt Wilkie wrote: > > Hi Fidel, > > The best way I know of to see how `@auto` works is to grab a .py from the > wild (e.g. hasn't been touched by Leo yet) and drag'n'drop it onto Leo's > body pane. Each `def` will become it's own node transparently, and when > saved the external file will not have any sentinels. > > *"**When reading @auto nodes, Leo creates the @auto tree using importers, > parsers that create an outline with nodes for each class, method and > function in the external file. Some importers create other kinds of nodes > as well.* > > *Importers presently exist for C, elisp, HTML, .ini files, Java, > Javascript, Pascal, PHP, Python and xml. Leo determines the language using > the file’s extension. If no parser exists for a language, Leo copies the > entire body of the external file into the @auto node."* > > See here in the reference guide for an extended description more: > http://leoeditor.com/directives.html#auto-path > > -matt > > > On Tue, Jun 25, 2013 at 1:38 AM, Fidel Pérez <[email protected]<javascript:> > > wrote: > >> Hi Matt: regarding the automatic hierarchy, does that mean that the node >> should break in subnodes and become a tree, or is it just an >> internal-non-visible process that makes leo manage the file contens >> differently? >> I just tried to save those as @auto, and restart leo, but nothing changed >> on them. >> Thanks. >> > >
-- 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.
