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.

Sign up for GitHub

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

Jump to bottom

Windows flake8 output is different than unixen #47

Open
msherry opened this issue Nov 12, 2019 · 1 comment
Open

Windows flake8 output is different than unixen #47

msherry opened this issue Nov 12, 2019 · 1 comment

Comments

@msherry
Copy link
Owner

msherry commented Nov 12, 2019

See #11 for the motivating report, but we should be able to handle output from Windows-run linters as well as OSX/Linux.
@msherry msherry mentioned this issue Nov 12, 2019
Closed
@sfavazza
Copy link

Hi I did some tests, and contrary to what you observed in the output I posted in #11, the output is the one from the error pipe and it's the same as the one of mypy or pylint.
Actually in linux it perfectly works, only in Windows for some reason the flake8 output is not parsed by flycheck.
I think I have to investigate directly the flycheck implementation...or probably just ensure that I have the last version of the *.el file.

Do you have any suggestion on how to step through the lisp file of flycheck when called?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@msherry @sfavazza