-
-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vista ctags get an empty windows with errors. #386
Comments
Can not reproduce. Use |
Here comes the vista.log for
|
I think it might be universal-ctags change something, I revert to the version about one years ago |
Okay, I found it. It seems you didn't use the same universal-ctags version as mine to test, that's why you can not reproduce the bug. After this commit universal-ctags/ctags@c0421c5 in universal-ctags repository, |
About the failed of |
@masatake The latest commit of u-ctags does not produce the $ ctags --format=2 --excmd=pattern --fields=nksSaf --extras=+F --sort=no --append=no --extras= --language-force=vim --vim-kinds=acfvmn --output-format=json --fields=-PF -f- autoload/vista.vim
# `name` field is missing
{"_type": "tag", "line": 5, "kind": "variable"}
...... |
I'm sorry. I changed. Instead of This means you should add optional fields you need to field enabled by default (A) or set all fields you need (B). Both A and B must work with the latest u-ctags and relatively older u-ctags. |
Thanks for the info @masatake, anything I can do in vista.vim to detect if the u-ctags is recent enough so that people using the older u-ctags won't complain? |
I don't find a good answer to the question.
In step 2., u-ctags reports which field is not available to stderr. |
You can send a pull request that includes test cases that verifies ctags behavior that vista.vim expects. |
Just tested
I'm happy to do that, could you point out where should I add such a test? @masatake |
I wrote an example test case for This is an interesting challenge for me to make an eco-system. I would like to apply this approach to other client tools. This is the first one. Inputs are welcome. |
I'll look into that tomorrow 👍, and happy to see vista.vim can be the first one of many in the future :(. |
I confirm this issue fixed in commit cdccc47. Should I report |
Please file a new issue, looks like the response of coc.nvim's API changed. |
<REMOVE ME> This is an example for a test case verifying ctags satisfies an expection of a client tool. * See <https://docs.ctags.io/en/latest/tips.html#tmain-a-facility-for-testing-main-part> to write and run a test case for Tmain target. * Use `Tmain: ` as the prefix of the header of the commit log. * Put files composint a test case to Tmain/client-<the name of client>-<aspect of testing>.d/ . * Put a README Tmain/client-<the name of client>-<aspect of testing>.d/ in addition to putting the standard Tmain test files like run.sh. The README is the message to developers of u-ctags. * Don't include unessary white-spaces in README and run.sh. </REMOVE ME> <REMOVE ME: MY TODO> I must write this to our docs. </REMOVE ME: MY TODO>
Tmain(client): add test for vista.vim (#2875) Ref liuchengxu/vista.vim#386 (comment)
Describe the bug
:Vista ctags
get an empty windows with errors.Environment:
Vista info
Steps to reproduce given the above info
**Steps and errors

The text was updated successfully, but these errors were encountered: