> Hello
> I load TAGS table with "visit-tags-table"
> Then place the cursor on a function name "Action()" in a C code and
> execute:
> etags-select-find-tag-at-point
>
> I receive the following information at the bottom of the screen:
> No exact match for tag "Action"
>
> Of course there are many functions with "Action()" name in my source
> code.
> I expect etags-select to show the list where I can choose the proper
> function definition to jump to.
> Is it right ?
>
> How to display such a list of function definitions to jump to, based
> on the tag the cursor is currently placed on ?
>
> Thank You for help ...

> Rafal Kurcz wrote:

>> Hello
>> I load TAGS table with "visit-tags-table"
>> Then place the cursor on a function name "Action()" in a C code and
>> execute:
>> etags-select-find-tag-at-point

>

>> I receive the following information at the bottom of the screen:
>> No exact match for tag "Action"

>

>> Of course there are many functions with "Action()" name in my source
>> code.
>> I expect etags-select to show the list where I can choose the proper
>> function definition to jump to.
>> Is it right ?

>

>> How to display such a list of function definitions to jump to, based
>> on the tag the cursor is currently placed on ?

> ...

> On 23 Lip, 15:23, Scott Frazer gmail.com> wrote:

>> Rafal Kurcz wrote:

>>> Hello
>>> I load TAGS table with "visit-tags-table"
>>> Then place the cursor on a function name "Action()" in a C code and
>>> execute:
>>> etags-select-find-tag-at-point
>>> I receive the following information at the bottom of the screen:
>>> No exact match for tag "Action"

> Rafal Kurcz wrote:

>> On 23 Lip, 15:23, Scott Frazer gmail.com> wrote:

>>> Rafal Kurcz wrote:

>>>> Hello
>>>> I load TAGS table with "visit-tags-table"
>>>> Then place the cursor on a function name "Action()" in a C code and
>>>> execute:
>>>> etags-select-find-tag-at-point
>>>> I receive the following information at the bottom of the screen:
>>>> No exact match for tag "Action"

>
> I've updated etags-select to work with the different tag types generated
> by etags. See the wiki page ...
>
> Scott

> Now the numbering of tags is very, very useful. Below are my
> conclusions about using etags-select:
> 1. It is very nice that it takes advantage of searchable mini buffer -
> especially in case of the long list of tags.

> 2. How to force etags-select to be case-sensitive.
> I've setup (setq tags-case-fold-search nil) and it works for M-. but
> unfortunately it does not work in etags-select.
> It is very important when browsing C/C++ code.

> Rafal Kurcz wrote:

>> Now the numbering of tags is very, very useful. Below are my
>> conclusions about using etags-select:
>> 1. It is very nice that it takes advantage of searchable mini buffer -
>> especially in case of the long list of tags.

>
> Yes
>

>> 2. How to force etags-select to be case-sensitive.
>> I've setup (setq tags-case-fold-search nil) and it works for M-. but
>> unfortunately it does not work in etags-select.
>> It is very important when browsing C/C++ code.

>
> Fixed, see EmacsWiki.
>
>
>

>> 3. It would be very nice to show more information in the list of tags.
>> For example VIM uses the following format to show the list of tags ...

>
> Great thanks for help Scott.
> Sorry for bothering you again but I think I found another weak point
> of etags-select.
> I started using it with the linux kernel's latest source tree.
> I generated the TAGS file:
> exuberant-ctags -R -e
>
> The size of TAGS file is 54 MB.
>
> Locating the tag with:
> etags-select-find-tag-at-point
>
> takes about 10s on Pentium 4 2.4 GHz.
> It takes about 15s when loading the TAGS table for the first time.
>
> Using the M-. takes about 0.5 s that is quite acceptable
>
> I did the test with Vim. ...

> Rafal Kurcz wrote:

>>
>> Great thanks for help Scott.
>> Sorry for bothering you again but I think I found another weak point
>> of etags-select.
>> I started using it with the linux kernel's latest source tree.
>> I generated the TAGS file:
>> exuberant-ctags -R -e
>>
>> The size of TAGS file is 54 MB.
>>
>> Locating the tag with:
>> etags-select-find-tag-at-point
>>
>> takes about 10s on Pentium 4 2.4 GHz.
>> It takes about 15s when loading the TAGS table for the first time.
>>
>> Using the M-. takes about 0.5 s that is quite acceptable
>> ...

> Scott Frazer wrote:

>> Rafal Kurcz wrote:

>>>
>>> Great thanks for help Scott.
>>> Sorry for bothering you again but I think I found another weak point
>>> of etags-select.
>>> I started using it with...