Ctags Error Tag Not Found
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the ctags next tag company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions
Ctags Ignoring Null Tag
Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million ctags not found in path programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Vim - ctags: tag not found up vote 14 down vote favorite 8 I want to use Ctags for a
Cscope Cstag Tag Not Found
Zend framework project. I executed this command : ctags -R ./* ../ZendFramework/*to create a list of tags, but the problem is when I press Ctrl-] on a class or method I get this error: ctags: tag not found I checked the tags file and all classes/methods/variables are listed. The tags files is located in the root of the project. Should I load it manullay when I open a file? vim ctags share|improve this e433 no tags file question edited Aug 15 '12 at 19:31 romainl 93.1k9115153 asked Aug 15 '12 at 18:51 user16948 1,02151729 1 For dealing with ctags you might want to use plugin Indexer: goo.gl/kixRn . It provides painless automatic tags generation for the whole project(s) and keeps tags up-to-date. Check my another answer for some details: goo.gl/pG9OP –Dmitry Frank Aug 16 '12 at 19:02 add a comment| 2 Answers 2 active oldest votes up vote 27 down vote accepted Yes, you should tell Vim where to find your tags file with something like: :set tags=/path/to/tags This is not very optimal, though. This line in your ~/.vimrc should help: set tags=./tags,tags;$HOME It tells Vim to look for a tags file in the directory of the current file, in the current directory and up and up until your $HOME (that's the meaning of the semicolon), stopping on the first hit. share|improve this answer answered Aug 15 '12 at 19:30 romainl 93.1k9115153 special thanks for semicolon! –lesnik Dec 8 '14 at 9:44 1 You might also find set autochdir useful. –crisron Dec 1 '15 at 16:51 add a comment| up vote 2 down vote The 'tags' variable must point to your tags file. See :help 'tags'. An example to add the path to your tags file: :set tags+=$HOME/yourpath/tags share|improve this answe
Support Search GitHub This repository Watch 458 Star 7,290 Fork 783 vim/vim Code Issues 267 Pull requests 43 Projects 0 Pulse Graphs New issue
No Tags File Cscope
incorrect parsing of exuberant ctags tags file #90 Closed GoogleCodeExporter opened this
E433 No Tags File Cscope
Issue Aug 18, 2015 · 4 comments Projects None yet Labels auto-migrated Priority-Medium Type-Defect Milestone No milestone Assignees No set autochdir one assigned 1 participant GoogleCodeExporter commented Aug 18, 2015 What steps will reproduce the problem? 1. cd into vim/src 2. Run ctags with case folding(ctags -R --sort=foldcase) 3. Open vim/src/main.c http://stackoverflow.com/questions/11975316/vim-ctags-tag-not-found 4. Either run: :set tags=tags Or your vimrc will need to be set to load the tags file 5. Go to line 208, and try to jump to definition for mch_fopen (CTRL-] is the specific command I'm using to try to jump) E432: Tags file not sorted: tags E426: tag not found: mch_fopen What is the expected output? What do you see https://github.com/vim/vim/issues/90 instead? I'd expect to follow jump to the definition of mch_fopen. I get the errors list above instead E432: Tags file not sorted: tags E426: tag not found: mch_fopen What version of the product are you using? On what operating system? Centos6 up todate as of yesterday vim hg pull -u from a few days ago Features: huge Both python and ruby enabled and pointing to pythonbrew and rvm installations VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 30 2012 16:11:40) Included patches: 1-712 ctags version: 5.8 Please provide any additional information below. If you look at the tags file you'll see a line at the top starting: !rm Which due to foldcase has been sorted before the "!_TAG_XXXXX" lines. This is valid tags file according to: http://ctags.sourceforge.net/FORMAT Written by Bram and Darren Hiebert Particularly: The names of the tags used in these lines may be suitably chosen to ensure that when sorted, they will always be located near the first lines of the tag file. The use of "!_TAG_" is recommended. Note that a rare tag like "!" can sort
Why doesn't XEmacs correctly locate the tag in the source file? 6. Why doesn't NEdit correctly locate the tag in the source file? 7. Why can't I jump to class::member? 8. How can I avoid having to specify my favorite http://ctags.sourceforge.net/faq.html option every time? 9. Why do I end up on the wrong line when I jump to a tag? 10. How do I jump to the tag I want instead of the wrong one by the same name? 11. What is Vim? 12. How can I locate all references to a specific function or variable? 13. Why does appending tags to a tag file tag so long? 14. How do I get regex support for Win32? 15. How should I set up not found tag files for a multi-level directory hierarchy? 1. Why do you call it Exuberant Ctags? Because one of the meanings of the word exuberant is: ex·u·ber·ant : produced in extreme abundance : PLENTIFUL synonym see PROFUSE Compare the tag file produced by Exuberant Ctags with that produced by any other ctags and you will see how appropriate the name is. 2. Why doesn't my editor work with these tag files? 3. What are these strange bits of text beginning with ;" which no tags file follow many of the lines in the tag file? These are "extension flags". They are added in order to provide extra information about the tag that may be utilized by the editor in order to more intelligently handle tags. They are appended to the EX command part of the tag line in a manner that provides backwards compatibility with existing implementations of the Vi editor. The semicolon is an EX command separator and the double quote begins an EX comment. Thus, the extension flags appear as an EX comment and should be ignored by the editor when it processes the EX command. Some non-vi editors, however, implement only the bare minimum of EX commands in order to process the search command or line number in the third field of the tag file. If you encounter this problem, use the option --format=1 to generate a tag file without these extensions (remember that you can set the CTAGS environment variable to any default arguments you wish to supply). Then ask the supplier of your editor to implement handling of this feature of EX commands. 4. Why doesn't XEmacs' Speedbar module work with Exuberant Ctags? The default command line switches used by XEmacs for etags are not compatible with Exuberant Ctags options. By default, Exuberant Ctags installs a symbolic link, "etags", pointing to the ctags executable. When Exuberant Ctags is started with the name "etags", it produces Emacs-style tag files by default. To fix this, add the