-
Notifications
You must be signed in to change notification settings - Fork 35
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
Taking too long vs regular cmd line #184
Comments
Also what I'm seeing is that the regular cmd line scan that I run generates around 2500 lines of code vs 50,000 when I do have atom generate it... |
I'm actually also looking for that piece of debugging advice. I've adjusted the excludes as well, but it seems they're having no effect. I'd love to see what |
Look at the tag-generator.coffee file. Specifically lines 51-52.
Regardless of how you configure the package, the .ctags is the file being used for the options. In my own project the above arguments (main bloat stemming from the It would be beneficial if there was an option to disable these options from being automatically added. If we customize the command and command arguments there should not be hidden additions to them. |
On macOS at least, the following command shows what command atom-ctags is running currently: ps -ef | grep ctags This may also help: https://stackoverflow.com/questions/821837/how-to-get-the-command-line-args-passed-to-a-running-process-on-unix-linux-syste |
My generation within atom continues to time out... I have excludes setup and I've tested them with regular command line ctags tool which takes 1-2 seconds...
Is there anyway to debug what's the actual cmd line that gets run by the extension? I feel like some parameters aren't being passed through.
The text was updated successfully, but these errors were encountered: