You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the command that I execute under the directory of my c++ project: ctags -R --c++-kinds=+p --fields+=iaS --extra=+q . /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1/
As you see, I use CTags for two directories: one is ".", which means the current directory, where I put all of my head files and cpp files. The other is "/Applications/..../c++/4.2.1/", which contains the head files of c++ standard library, such as "iostream".
However, after executing the command above, it can't popup std::cout. Meaning that when I type std::, I can't find cout.
Then I tried to add all of options: --c++-kinds=+cdefglmnpstuvx.
Now I can get cerr and endl when I type std::, but I still can't get std::cout or std::cin.
The text was updated successfully, but these errors were encountered:
I'm using CTags on Mac OS for c++ projects.
Here is the command that I execute under the directory of my c++ project:
ctags -R --c++-kinds=+p --fields+=iaS --extra=+q . /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1/
As you see, I use CTags for two directories: one is ".", which means the current directory, where I put all of my head files and cpp files. The other is "/Applications/..../c++/4.2.1/", which contains the head files of c++ standard library, such as "iostream".
However, after executing the command above, it can't popup
std::cout
. Meaning that when I typestd::
, I can't findcout
.I've found a relative question: http://stackoverflow.com/questions/3655743/when-using-exuberant-ctags-what-options-to-you-use
Then I tried to add all of options:
--c++-kinds=+cdefglmnpstuvx
.Now I can get
cerr
andendl
when I typestd::
, but I still can't getstd::cout
orstd::cin
.The text was updated successfully, but these errors were encountered: