-
Notifications
You must be signed in to change notification settings - Fork 365
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
No maker should be enabled by default. #2515
Comments
Good point. But I can see that especially with C files this is not the case, and often you get warnings from clang when headers are not configured / picked up properly etc. |
Yes. The other day when I opened a latex file with vim, the maker called |
Do you have some example output for what is not considered useful?
|
I have not used this tool in years. |
@nate-onesignal I see, sorry for the noise then - maybe you can still say something about using |
As for latex, I agree that no makers should be enabled by default. Many issues have been raised before for latex filetype like #243 #3470 in SpaceVim I think
I think everyone who writes latex in vim will use some other plugins like My workaround now is to use
|
Thanks for the feedback!
That's good, and something I also use with "c" files IIRC by default. |
Maybe there could/should be a global setting to enable/disable suggested default makers (which could/should still get revisited/improved in general), but would allow to easily have an opt-in-only situation, which is what the issue is about initially. |
I also need to selectively enable certain makers (based on filetype in my case). Here's the only approach I can make it work:
Basically, on buffer enter, disable neomake by default. Then based on certain condition, enable it again. |
Some makers are enabled by default in Noemake. This means they will be running even if the user does not expect it. Some of these linters are buggy, polluting the user's location lists with false positive of warnings, even error messages from the linters themselves. The user is often left no option but modifying his
vimrc
file to explicitly disable them. Forcing the user to disable something he may have not heard of doesn't seem right.The text was updated successfully, but these errors were encountered: