Hi Mike,
this does not work: I get the same result as below, for a.el just one node
named 'a declarations'

Bye and thanks
Enrico

On Tue, Mar 31, 2009 at 1:20 PM, Mike Crowe <[email protected]> wrote:

>  Hi Enrico,
>
> Did you try:  File -> Import -> @file?  There is a lisp importer, and that
> should work.
>
> Mike
>
>
> Enrico Spinielli wrote:
>
> Hi,
> I would like to import a lisp file, say an Emacs lisp one a.el.
> I tried to define a node like
> @auto D:\a.el
>  I then issue File --> Read/Write...-->Read @auto Nodes
> I was expecting an outline with child nodes for each
> function and one for anything else named '<filename w/out extension>
> declarations'
> but I just get the last one only.
>
> In fact this was my very first investigation towards being able to get a
> readonly outline out of
> a (common) lisp and being able to reference as comments some of its
> functions/constants/...
> in some Python source...
>
> Any help is super welcome
> Bye
> Enrico
> --
> Enrico Spinielli
> "Do Androids dream of electric sheep?"— Philip K. Dick
> "Hear and forget; see and remember;do and understand."—Mitchel Resnick
>
>
>
> >
>


-- 
Enrico Spinielli
"Do Androids dream of electric sheep?"— Philip K. Dick
"Hear and forget; see and remember;do and understand."—Mitchel Resnick

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to