-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
clang-check generating plist files #703
Comments
This has been mentioned before in other plugins: kumar8600/flycheck-clangcheck#5 I don't know much about |
I did some digging and if you add the arguments |
I don't understand this behaviour. Can you point me where you found the solution and confirm the issue ? I couldn't reproduce the behaviour on a project of mine, and running For info :
I built llvm from versioned source on Feb 6th |
The issue occures when you don't have a build directory. This is the default implementation of clang-check in ale. It could be probably tuned for a case by case basis but that is very cumbersome especially if are editing multiple small projects. /bin/bash -c clang-check -analyze <filename> |
You could create a build directory or .gitignore the plist files. |
Maybe those arguments for disabling the plist files could be added if no build directory is detected. |
Personal opinion so please take it with a grain of salt. I think making it so that if no build directory is detected it adds those arguments is the best way to approach this problem. I'll try and learn som vim script to see if I can figure out how to fix this but vim script is a language I've never worked with. |
It doesn't look too difficult to do then. As of now all clang linters check for
So the block where to add these default options is clearly defined if I'm not mistaken : Clang-check needs a little more work, since there is a ternary conditional operator instead of having a true |
Yeah, I think setting those options if the build directory isn't detected is the way to go. If we find one, then we won't generate the files because we're using the build directory. If we don't, then we won't generate those files because those options are set. |
@mkarpoff I pushed a commit for this now with some tests. Give it a try, and let me know if it works properly. Now those arguments should be added if and only if there's no build directory set. |
Looks good so far. Thankyou so much for the fix and for this plugin it is amazing. |
* upstream/master: Filter the completion results by the prefix we used dense-analysis#703 Add arguments to avoid generating plist files if no build directory is detected for clang-check
In one of the recent (last couple of weeks) something changed and when I open a cpp file a new file is always generated. It always is a match for the cpp file IE.
helper.cpp
generateshelper.plist
. I did some digging and I think it is because clang-check isn't run on a tmp file but the original file itself. I ran clang-check using the arguments it runs with (Found those using ALEInfo) and the same bahaviour happens.The text was updated successfully, but these errors were encountered: