tags/tips completion

[Bert Wesarg]

Hello,

On Wed, Feb 27, 2008 at 10:06 PM, Joerg Fischer <jf505 at gmx.de> wrote:
>
>  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
>
Thanks for the pointer, and like thorsten I missed this patch totally.

>  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.
Ok, if performance is a question I'm with a special function to filter
tags/tips.

The problem with regex search could be made optional with an
search_type argument which could be "regex", "prefix", or even
"suffix", "literal" could be only useful to check whether a tag/tip
with this name exists. default would be "prefix", or?

 => list_tags(mode, file [, stub[, search_type]])
>
>  If it is only about the name, how about list_tags(mode, file [, stub])?
Can you give some rationals for the 'mode' argument, and why not two
functions (I stick for this with your name suggestion): list_tags()
and list_tips()? The only advantage could be a "booth" mode, or? But
thats silly, because file is either a tags or a tips file.

Could it also be useful to retrieve tags/tips from all loaded files?

So, I ended up with this:

list_{tags,tips}([file ][, stub [, mode]])

but I don't know if this is doable.

Bert
>
>  Jörg