> Such a behavior most likely is far from one's expectations. Though, there is > no any riddle here, just the latest version of exuberant ctags cannot parse > new extensions to VIM script.
It can't parse function autoload#blah#foo#method, either. So if you want to include this into your patch, too? It's only a hack there might be better solutions but it should work fine 99c99,102 < if (isupper ((int) *cp) || scope == 's' || scope == '<') --- > if (isupper ((int) *cp) || > islower ((int) *cp) || // this is because > of the new autoload style fun ab#Upper() (folders may start with lower case > letters) > > // I think its useful if the location is included into the tag > scope == 's' || scope == '<') 105c108,109 < } while (isalnum ((int) *cp) || *cp == '_'); --- > } while (isalnum ((int) *cp) || *cp > == '_' || *cp == '#' ); > // '#' is sed in the new autoload > mechanism. see :h autoload in vim help Marc
