-
Notifications
You must be signed in to change notification settings - Fork 9
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
setup.cfg ignored #24
Comments
Hi!
We could change this linter to work with the real files on disk only. (It would only run on save, not in the background anymore.) There is also a dead PR over there which will enable support via stdin. In that case, the proposal is that the user has to specify the config manually bc |
Hi, P.S. I also tried other linter with same config, and it works:
Using this config, pydocstyle does not ignore warning, but |
For project settings, you would set
Or globally, in the SublimeLinter user settings:
|
Thanks, that does work now. |
It's not super elegant that it doesn't work out of the box. The tempfile solution has, IMO, too much unexpected behavior and downsides to be a good default. We should think about that a bit more for SL 5. But here it does work if you know how to set it up at least. |
I have this config called
setup.cfg
:I have directory
source
where are my projects located andsetup.cfg
file too. Like this:When I open sublime and it runs linter, I see that it ignores my
setup.cfg
and still throws warning aboutD100
:Though if I manually run linter like :
pydocstyle machine/models/machine.py
. It does check mysetup.cfg
and does not throw warning about D100 (for testing purposes I ran it from same directory as sublime linter indicated looking ->/home/oerp/odoo11/source/personal/oerp-odoo
).P.S. Though for example I have
eslint
configuration which uses same approach and it works. I wonder why this one is ignored?The text was updated successfully, but these errors were encountered: