ctags

I'm using ctags for keyword completion on a PHP project in vim. Since ctags doesn't handle PHP namespaces out of the box, I've added a regex option to my ctags command: ctags (...) --regex-PHP='^namespace\s+([^;]*)/\1/c/' (...) This works fairly well: if I type Foo<Ctrl+N> I get suggestions for Foo , Foo\Bar , Foo\Bar\Baz and so on. However, the backslash seems to count as a word separator when vim determines the keyword to look up in the tags file. In other words, typing Foo\Ba<Ctrl+N> does not give me suggestions for Foo\Bar\Baz etc, which is what I wish. It will only suggest tags that

I'm getting "skipping XXX: it is not a regular file" every time I run ctags -R XXX . For one reason or another, ctags on Cygwin isn't recursing directories. Surely, I must be doing something stupid. Whenever I try the de-facto standard ctags -R in my project root, it complains that I didn't specify any input files. When I specify a directory, it seems to think its a file. I'm a tad stumped. I installed a fresh Cygwin build last week from scratch. I installed everything. I rarely use Cygwin. ctags works perfectly on all my BSD, Linux, Mac and Solaris boxes. I thought Perforce's read-only

I generate ctags with the following command ctags -R --fields=+l --languages=python --python-kinds=-iv -f ./tags apps/employees/models.py and this is my code from django.contrib.auth.models import AbstractUser from django.contrib.postgres.fields import HStoreField from django.core.validators import MaxValueValidator, MinValueValidator from django.db import models from django.utils import timezone from django.utils.translation import ugettext_lazy as _ from author.decorators import with_author from django_extensions.db.models import TimeStampedModel from django_fsm import FSMField from imagekit

I try to create tags for a wiki-file = vimwiki. This is my definition for ctags, stored as ctags.cnf --langdef=vimwiki --langmap=vimwiki:.wiki --regex-vimwiki=/^=[ \t]+(.*)/\1/h,heading1/ --regex-vimwiki=/^==[ \t]+(.*)/2-\1/h,heading2/ --regex-vimwiki=/^===[ \t]+(.*)/3-\1/h,heading3/ --regex-vimwiki=/^====[ \t]+(.*)/4-\1/h,heading4/ Calling ctags --verbose index.wiki results in: ... Considering option file .\ctags.cnf: reading... Option: --langdef=vimwiki Option: --langmap=vimwiki:.wiki Setting vimwiki language map: .wiki Option: --regex-vimwiki=/^=[ \t]+(.*)/\1/h,heading1/ Option: --regex

编写者：龙诗科 邮箱：longshike2010@163.com 2016-01-06 众所周知，windows下的source insight是阅读项目代码的神器，其神奇之处在于可以根据当前鼠标所指的函数名或者变量，来进行全局搜索该函数或变量的定义，而且还会显 示出哪些文件中同样含有该函数定义，另外可以显示当前文件中的变量和函数列表。因此特别适合在windows下用source insight 来进行大项目代码阅读和管理。但是Linux下不能 安装source insight,而vim和Emacs是linux下编辑代码的神器，其vim的功能可以通过一系列的插件来扩展，很方便，且都是开源的，通过一下午的折腾，终于完成了简单而又强 大的vim环境搭建，当然自己为了培养码农能力，并没有安装代码补全的功能插件，折腾之后的效果图如下： 我用的 ubuntu14.03LTS版本，之所以没有用 14.10是因为国内的很多软件源都不支持该版本的升级，当你安装好了 ubuntu之后，默认已经安装了 vi，这时候，你自己先得安装 vim，在终端输入以下命令即可： sudo apt-get install vim 这时，你可以用以下命令来检测是否安装成功： vim --version 然后就是安装插件了，这里主要参考了以下三个博客文章： 将你的 Vim打造成轻巧强大的 IDE 改造 vim编程

I am new to Tcl/Tk, I am using Vim to code and browsing. The syntax highlighting for Tcl/Tk is working fine. The jump into the function using Ctrl ] doesnt work it gives me an message saying that " cstag: tag not found ". I have installed ctags and generated tags using " ctags -R *.tcl ". I have extensively used namespaces in Tcl/Tk code. The tags generated in tags file is something like this " namespace1::function1 ". How do i get Ctrl ] (and Ctrl T for popping from stack) working in Vim? The function to jump could be in either of the 2 formats shown below function1 namespace1::function1

I'm new to ctags. After reading some information about the program, I concluded that "Universal ctags" is the newest version (successor of "exhuberant ctags") and still under active development: https://ctags.io/ Most people use it on Linux. For some specific reasons I need to use it on Windows (Windows 10, 64-bit to be more precise). I'm looking for an executable file of Universal ctags. Do you know where to download such an executable? PS: I'm not interested in the cygwin-approach (again for some specific reasons, but that would lead us too far here). EDIT: For a better understanding of