Repository navigation
optmux-find --tags-path: no wait on the first build - #73
Merged
Merged
Conversation
The first call used to wait up to 120s for ctags, stalling vim at startup. It now prints the .abs.tags path immediately (empty until the build is done); the background build writes the absolute-path copy when it finishes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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 first
--tags-pathcall polled up to 120s for ctags, so vim paused at startup. It now prints the.abs.tagspath at once (an empty file until the build finishes); the background build writes the absolute-path copy when done, and vim picks it up at its next tag lookup.Tests: new test for the no-wait path; full suite passes.
🤖 Generated with Claude Code