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

Consider adding sym table export to ctags #170

Closed
jackkinsella opened this issue Jan 8, 2019 · 3 comments
Closed

Consider adding sym table export to ctags #170

jackkinsella opened this issue Jan 8, 2019 · 3 comments

Comments

@jackkinsella
Copy link

I'm using starscope to generate ctags which in turn powers my auto-complete in vim. This works majestically for function definitions and constants, but it doesn't pick up symbols.

For example, in Rails I might write:

   has_many :orders, dependent: :restrict_with_exception

With the current workflow, the :restrict_with_exception symbol will not be available in other buffers.

What are your thoughts on adding syms to the ctag format exports? Or at least allowing an option for this. Happy to make a PR if this is something you'd consider.

@eapache
Copy link
Owner

eapache commented Jan 8, 2019

I'm happy to consider it, but I'm not sure where in the ctag format symbols would fit in, since (unlike the others) they don't have a single canonical point of definition, they just get used.

@jackkinsella
Copy link
Author

jackkinsella commented Jan 8, 2019

You're right. It sort of breaks the semantics. Perhaps there could be an option to export a general sym list into a plaintext file that could be read as a source for autocomplete plugins.

For example:

:set complete+=.starscope_syms

@eapache
Copy link
Owner

eapache commented Jan 8, 2019

Ya, something like that would probably work. You might also be able to get what you want via the cscope export?

@eapache eapache closed this as completed Mar 18, 2019
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

No branches or pull requests

2 participants