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

Allow custom .ctags file to be specified in settings #179

Open
jclark-dot-org opened this issue Aug 22, 2017 · 2 comments
Open

Allow custom .ctags file to be specified in settings #179

jclark-dot-org opened this issue Aug 22, 2017 · 2 comments

Comments

@jclark-dot-org
Copy link

I have some extra ctags settings I use currently by modifying ~/.atom/packages/symbols-tree-view. Whenever the package is updated, my changes are overwritten. I'd prefer to specify a separate .ctags file in settings that I could maintain outside the package structure, preventing the loss of changes during updates.

@nicolashainaux
Copy link

Could you tell more about your extra settings? Could they be simply included in the provided ctags file?
And I'm not sure, but this looks close to the issue there nicolashainaux#13 (-> could this be a solution to your issue?)

@jclark-dot-org
Copy link
Author

I work with Salesforce.com's Apex language, which is close enough to Java that using ctags' Java settings gives acceptable results in symbols tree view. The source files are .cls files instead of .class, so ctags doesn't recognize it by default. Currently I add one line to ~/.atom/packages/symbols-tree-view/.ctagsto treat .cls files as Java:

--langmap=Java:.cls

I believe this could be added as an arg to ctags, so the linked issue might be sufficient. Eventually I'd like to build better Apex support using --langdef and a set of Regexes, at which point an accessible .ctags file might be easier due to volume, but the option to add command line args is a good solution for now.

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