Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

options support by {type} / buffer local options #264

Open
promisedlandt opened this issue Feb 26, 2020 · 2 comments · May be fixed by #350
Open

options support by {type} / buffer local options #264

promisedlandt opened this issue Feb 26, 2020 · 2 comments · May be fixed by #350

Comments

@promisedlandt
Copy link

For a while, ripper tags (for Ruby) was supported by adding following options like this: let g:gutentags_ctags_executable_ruby = 'ripper-tags --ignore-unsupported-options --recursive'

(see this comment).

This does not work anymore, because the executable is now passed as the whole string, and of course there is no executable called 'ripper-tags --ignore-unsupported-options --recursive.
Options are now passed separately, but setting them as let g:gutentags_ctags_extra_args = ['--ignore-unsupported-options'] breaks all non-ripper invocations, because ctags dies with ctags: Unknown option: --ignore-unsupported-options.

In other words, the extra options only make sense with the ripper-tags executable.

Would it be possible to add either g:gutentags_ctags_extra_args_{type} or use buffer local b:gutentags_ctags_extra_args so it's possible to set it in after/filetype/ruby.vim ?

@smati-checkr
Copy link

smati-checkr commented Mar 17, 2020

👍 Facing the same issue.

Not entirely sure why g:gutentags_ctags_executable_ruby functionality was taken away without a robust alternative.

@ludovicchabant
Copy link
Owner

The functionality was taken away without a robust alternative because I just didn't think of it :)

FYI, the change was caused by the giant mess that is whitespace handling in shell scripts, for people who put vim files/projects/gutentags in directories with spaces in them.

So yes you're right we need to add a g:gutentags_ctags_extra_args_{type} option.

@MaxGyver83 MaxGyver83 linked a pull request Jul 29, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants