Mailing List efte-dev@2rosenthals.com Archived Message #44

From: "Gregg Young" <efte-dev@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [eFTE-dev] Ctags
Date: Mon, 01 Jan 2018 15:40:32 -0700 (MST)
To: "eFTE Developers Mailing List" <efte-dev@2rosenthals.com>

Hi,

<snip>

>OK, now I see what you were trying to do.
>
>"ctags --list-kinds=c++" outputs:
>
>>c  classes
>>d  macro definitions
>>e  enumerators (values inside an enumeration)
>>f  function definitions
>>g  enumeration names
>>l  local variables [off]
>>m  class, struct, and union members
>>n  namespaces
>>p  function prototypes [off]
>>s  structure names
>>t  typedefs
>>u  union names
>>v  variable definitions
>>x  external and forward variable declarations [off]
>
>You can add C++ function invocations to the ctags
>config file, ".ctags". Assuming function invocations
>always look like an equal sign followed by [spaces or
>tabs and] some alphanumeric string plus an opening
>parenthesis, and the above doesn't conflict with the
>definitions of the other tag "kinds" for C++ (can't check
>right now), you would need something like this in
.ctags:
>
>--regex-c++=/=[
\t]*([A-Za-z0-9_-])+\(/\1/i,inv,invocations/
>
>And then you'll get function invocations in your TAGS
>file.
>
>Hope this helps.
>

Yes. Thanks for the mini-tutorial.

I am actually fine with it the way it is. I just
misinterpreted the help file. My issue was if efte was
performing as designed or not. It appears it is in this
regard.

Gregg

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster