Generate a tags file for navigation while editing #126
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
There aren't any headings or grammatical category names today that include a slash, and there aren't likely to ever be any. This change prevents generating incorrect search patterns in the tags file in the future, just in case, and it's better to be correct anyhow.
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.
The output uses using the POSIX ctags syntax, and enables "jump to definition" for DocC links and for syntactic categories in the formal grammar. From testing with a few different editors, here's what I saw:
setlocal iskeyword+=#,:,-to allow those characters as part a tag. Then both links and grammar works. Classicvisupports tag files, but doesn't haveiskeyword, so othervi-like editors might not be able to follow tags.-as part of a tag.Marking this as a draft for now. I'd like to consider rewriting the script in Swift.