I have a copy of ctags installed system-wide. symbols-view also include of copy of that program, but of course it may not be the same version. If my system-wide version understands some extra arguments the bundled version doesn't, and I use those in my ~/.ctags file, the bundled ctags will just fail.
This is a slight design decision, but I think you should invoke the bundled ctags such that it ignores the ~/.ctags file by default. Perhaps make it an option to use that file (for people who want that), with a mention of the version of ctags bundled. Complicated customizations of the bundled ctags could be done with a separate, atom-specific config file.
I have a copy of
ctagsinstalled system-wide.symbols-viewalso include of copy of that program, but of course it may not be the same version. If my system-wide version understands some extra arguments the bundled version doesn't, and I use those in my~/.ctagsfile, the bundledctagswill just fail.This is a slight design decision, but I think you should invoke the bundled
ctagssuch that it ignores the~/.ctagsfile by default. Perhaps make it an option to use that file (for people who want that), with a mention of the version of ctags bundled. Complicated customizations of the bundled ctags could be done with a separate, atom-specific config file.