-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Question] is citre-tags-file-alist gone? #180
Comments
See the documentation. We've switched from If you can't put |
Thank you. I should read the document before opening this issue. What citre does in I want to have a shell command just doing encoding:
So I can do
is more joyful. Just for "encode", we can reimplement the encode function in any language. |
After thinking again, ~/.cache/tags/ is not only about citre but all tools related to tags files. We can assume it is a protocol between tags(5) generators and client tools. I want to add -O option to ctags and -T option for readtags. If |
Ah, this idea is quite similar to what GNU Global has implemented. In
In
The convert style is different from Citre. Database of |
Today, I did
cd citre; git update
. Then, citre didn't work.I found that
citre-tags-file-alist
is gone.I have added more than 100 elements on the list...
After some studying the latest citre, It seems that I should put a tag file for the source tree ~/.cache/tags with specially encoded file name like !home!yamato!var!cpython!.tags. Am I correct?
I will learn the way to run ctire ctags for generating and managing tag files as a ctags user. However, I, as a ctags developer, would like to establish the workflow generating a tag file by running ctags directly.
The source tree I want to inspect is on a read-only file system.
The text was updated successfully, but these errors were encountered: