Bert Wesarg wrote: > Hmm, in my sense 'generic' means 'without a special purpose' but your > function name doesn't fit to this: its sounds very special to > completion. If you would call the find_completions() function like > get_tags/tips_from_file() (or get_definitions_from_file(mode)), and > this functions do only that, and a separate function which returns > 'completions' from a arbitrary string list, that would I call generic > and would be more useful for others, not only completion.
There is an old patch in the tracker written before the calltips feature and conflicting with it http://sourceforge.net/tracker/index.php?func=detail&aid=520509&group_id=11005&atid=311005 Basically, I created only a light version of it. A regex search on each piece of tag looks a bit inefficient. Although I didn't try, I would be surprised if it runs fast on anything but very small tag files. If it is only about the name, how about list_tags(mode, file [, stub])? Jörg -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
