Skip to content
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

tags: Follow up with upstream change of the input field #146

Open
AmaiKinono opened this issue Jan 20, 2023 · 0 comments
Open

tags: Follow up with upstream change of the input field #146

AmaiKinono opened this issue Jan 20, 2023 · 0 comments

Comments

@AmaiKinono
Copy link
Member

Several changes has been introduced to readtags and the tags file format to solve universal-ctags/ctags#3559, which basically means:

  1. The input field has to be parsed differently based on TAG_OUTPUT_MODE and TAG_OUTPUT_FILESEP ptags.
  2. When writing a pseudo tag to a tags file, we have to escape things differently based on how the input field is parsed, which is based on TAG_OUTPUT_MODE and TAG_OUTPUT_FILESEP.

1 can be solved rather easily. Solving 2 will add considerable complexity (The "right" way to solve 2 should be creating an "edittags" command-line tool).

Since Citre only writes a CITRE_CMD ptag for now, I suggest just get rid of it and use a separate file to store the command line (like {tags-file-name}.cmdline in the directory of the tags file).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant