1.) Lisp level functions are handled anyway by the jump to documentation script. 2.) It's only a problem when jumping as you then jump to the incorrect file but since I don't do much global functions anyway this is not a problem for me, if I jump to http for instance I end up in the right file. 3.) Correct and could become a potential annoyance when jumping, unfortunately my autocompletion only locks on to the predefined lisp functions and all definitions in all open buffers so there it is not a problem (I was wrong before when I wrote in my article that it would lock on tags too).
On Tue, Nov 15, 2011 at 12:22 AM, Alexander Burger <[email protected]> wrote: > Hi Henrik, > >> Not much to it, I do things "old school" ie I put the download in >> /opt/picolisp and simply cd there in a shell and do: ctags -e -R >> --languages=-JavaScript,-PHP,-C,-Make,-HTML >> >> This will recursively loop through all the folders and generate tags >> for everything, for instance all my projects in /opt/picolisp/projects >> and the standard library in /opt/picolisp/lib > > I see. However, I would see some problems with that: > > - 'ctags' doesn't know how to handle the Lisp level functions like '*/', > and their connection to 'doMulDiv'. > > - In the folders may be several files that contain a (de foo (..) ..), > and 'ctags' doesn't know which are loaded in the current project. > > - 'ctags' cannot resolve methods with the same name for different > classes, and associate each of them with its class. > > If you simply let the PicoLisp runtime do it, you have it all in the > right place. > > Cheers, > - Alex > -- > UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe > -- UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
