Skip to content

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

@AmaiKinono

Description

@AmaiKinono

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions