Allow custom language definitions #876
Merged
Conversation
This file contains hidden or 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
Contributor
Author
|
I added a commit to check if the language is recognized by ctags, and only include the first |
Arhinebeneze1
approved these changes
Jun 10, 2025
derbroti
pushed a commit
to derbroti/tagbar
that referenced
this pull request
Jul 6, 2025
* Add second --option directive * Only add first --options for custom language * Save supported_types to avoid extra ctags calls --------- Co-authored-by: Andy McAliley <AndyMcAliley@users.noreply.github.com> Co-authored-by: Andy McAliley <wmcaliley@usgs.gov>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes #789
This PR adds a second duplicate
--optiondirective to thectagscommand, usingdeffiletwice. The first--optioncomes prior to--language-forceand lets ctags know the custom language. The second--optioncomes last to override the default--kinds-<lang>definition.This PR addresses the same problem that #792 addresses, but in a different way that doesn't require additional user options.
This fix needs testing, especially on the use case described in #776.