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

Report error after find invalid options #1378

Closed
zhihuiFan opened this issue Mar 13, 2020 · 2 comments
Closed

Report error after find invalid options #1378

zhihuiFan opened this issue Mar 13, 2020 · 2 comments

Comments

@zhihuiFan
Copy link

Is your feature request related to a problem? Please describe.
Right now, the issue I am facing is when I run rtags-find-sysbol and type some prefix then tab, I can't get any auto completion. usually I can.
some days ago, my autocompleted doesn't work for aStruct->, the final reason probably there are some gcc options which clang doesn't know. anyway, I didn't change any emacs settings, the issue gone.

So this requests is for a feature that rdm can auto detect some invalid settings in compile_commands.json, for example: there are 2 entires for the same file or there are some complier options for clang in compile_commands, so that user can fix it quickly.

Describe the solution you'd like

rdm --validate_cmdb will reports all the issue like above.

Thank you for this project always!

@zhihuiFan
Copy link
Author

BTW, My emacs configuration for rtags is not changed for a very long time, but some times the rtags-diagnostics can work automatically (means when I am typing, it show me the something wrong in time), but some times, it can't. However the rtags-compile-file can still work (and only one line for this file in compile_commands.json. What maybe the reason?

Thanks

@zhihuiFan
Copy link
Author

So this requests is for a feature that rdm can auto detect some invalid settings in compile_commands.json, for example: there are 2 entires for the same file or there are some complier options for clang in compile_commands, so that user can fix it quickly.

The easiest way to detect invalid options is change the "gcc" to "clang" in compile_commands.join, and run rtags-compile-file command. we will get an clear error if we have one.

Another way to avoid such situation is just use clang to compile our software. that's the way I'm using 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

1 participant