format-3: update (merge the master branch) #1736
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…put-format=u-ctags|e-ctags option To record meta characters like tab in a name, we have designed new file format. The file format itself was already introduced. TAG_OUTPUT_MODE pseudo tag was used as marker telling which format is used in a tag file: Exuberant-ctags(e-ctags) compatible format or Universal-ctags(u-ctags) file format. u-ctags was the default format. A user could choose the format with --output-format option. However, we recognize that the hack using TAG_OUTPUT_MODE pseudo doesn't work well with readtags command. A data structure of readtags doesn't have a field for recording TAG_OUTPUT_MODE. It means readtags cannot switch the file format version dynamically. The pseudo tags can be used in readtags for the purpose, recognizing the file format is only TAG_FILE_FORMAT. This commit introduces following SELF INCOMPATIBLE changes: 1. --output-format=u-ctags and --output-format=e-ctags are removed. They are unified to --output-format=ctags. 2. TAG_OUTPUT_MODE pseudo tag is removed. Instead TAG_FILE_FORMAT=3 is introduced. TAG_FILE_FORMAT=2 is compatible with e-ctags. TAG_FILE_FORMAT=3 is default. A user can choose one of the formats with --format=3 or --format=2. The new "version 3" may break many client tools. If you are just user of such client tools, use --format=2 option to generate tags file with compatible file format. If you are a developer of such client tools, please, consider to support --format=3. The rest of work are: 1. more Tmain test cases, 2. more precise documentation about the format 3. 3. updating readtags to support format 3. About readtags, the most of all work is done by @b4n. I must merge his changes(universal-ctags#1605). docs/news.rst are rewritten by @b4n and @codebrainz. Ussing stringfy for printing default version of file format in --help message is suggested by @b4n. Signed-off-by: Masatake YAMATO <yamato@redhat.com>
[SELF INCOMPATIBLE] main: introduce version 3 format and remove --out…
Merge the latest changes on master branch
Merge the latest changes in master branch
Merge the latest changes in master to format-3 branch
Update Format-3 branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.