Clément Pit-Claudel

Can you try replacing `"--stdin-filename" source-original` with `(option "--stdin-filename" buffer-file-name)`?

Perfect, if number 4 works then that's what we should use. Thanks a lot for testing. (The differences with the others are subtle: they depend on exactly what ruff does...

Sorry, didn't mean to close

Perhaps we should do the same thing for other checkers that depend on an stdin filename. I suspect that the same issue would pop up in most of them.

Right, you'd need to add ``` :error-filter (lambda (errors) (flycheck-sanitize-errors (flycheck-remove-error-file-names "-" errors))) ``` Maybe that too should be the default when using `:standard-input t`

This works for me: ``` (flycheck-define-checker python-ruff "A Python syntax and style checker using the ruff. To override the path to the ruff executable, set `flycheck-python-ruff-executable'. See URL `https://beta.ruff.rs/docs/'." :command...

> Yup. Thanks a lot! > I don't know how you did it, but it works. I ran ruff on the command line. If you don't pass it a filename,...

https://github.com/flycheck/flycheck/pull/2065

Thanks for the detailed report :heart_eyes: The warning is computed by the Emacs bytecode compiler, not by Flycheck itself. You can use M-x flycheck-compile to see exactly how it is...

See `flycheck-emacs-lisp-load-path` maybe?