C extensions tags
update
#26
Open
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.
Hi,
I'm playing with ruby C extensions + browsing ruby source (also related to tpope/rbenv-ctags#5) and I notice an issue: after tags are used once to jump to ruby source or include dir, vim's
tags
option looses tags for ruby C source.This is a bummer, because the majority of C functions or macros "exposed" to users via
ruby.h
almost always delegate to some internal ruby functions.. So in most cases a single tags jump is not enough.I compared how this works when editing ruby files and then making a tags jump to ruby std lib. In this case
tags
option is handled nicely.This PR contains a proof of concept solution for the problem: if a user opens a ruby C extension file an autocmd is registered (once). While vim's
cwd
is inside a ruby project,path
andtags
options for C files will be updated.Feedback is appreciated!