Bert Wesarg wrote: > 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.
Well, yes, I have such an interface in the sense that the built-in variables $loaded_tags/tips_files are part of the mocume patch. The find_completion() function is a generic built-in macro function, although I didn't submit a patch for this one, yet. It's documentation is find_completions( mode, filename [, stub] ) Returns a string containing a newline separated list of either tag or tip names from the loaded tags or tips file given by filename (the full name including the path) that are completions of the optional string stub, where mode is either "tags" or "tips", respectively. If stub is not given or empty, all the tag or tip names in the file are returned. If no completions are found (or filename isn't in $loaded_tags_files or $loaded_tips_files), an empty string is returned. So, all the information you request, except for the tips text which isn't loaded to the hash table but looked up from the respective file each time, is there. Cheers, Jörg -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
