On Wed, Feb 27, 2008 at 4:49 AM, Joerg Fischer <[EMAIL PROTECTED]> wrote:
> Bert Wesarg wrote:
>
>  > do you plan to introduce some tags/tips information macros, like these
>  > for highlight/rangesets? I may also interessted in these.
>
>  My plan isn't to provide a pure macro solution, but to make more of
>  nedit accessible to macros.  This is also the main idea behind the
>  mocume patch, btw.
>
>  For a tag completion, I thought one could quickly get out all possible
>  extensions from a loaded tags file.  This is the find_completions()
>  part [named after find_definition() - list_completions() was a typo],
>  and I can confirm it is fast.  Then one may have to look up things
>  like scope information from the tags file to further exclude some of
>  the possible completions.  These parts are done inside the macro.  It
>  needs to know the loaded tags files, though.  This is rather simple by
>  introducing $loaded_tags/tips_files array variables containing the
>  names of all currently loaded tags/tips files, with integer keys
>  starting at 0.
This was the answer for my question: A macro interface to the
tags/tips database, ie loaded files, tags/tips loaded from these
files, tips text, tags location (file, line or search pattern, ...),
...

with this generic macro interface to this db, you can easily build
your completion. And your find_completion() function should also made
generic, ie given a list/array of strings and a prefix and return all
prefix-matches.

Bert
>
>  Cheers,
>  Jörg
>  --
>  NEdit Develop mailing list - [email protected]
>  http://www.nedit.org/mailman/listinfo/develop
>
-- 
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to