Hi, with flycheck 0.22, the php-phpcs checker doesn't run on buffer.

First I run flycheck-select-checker and choose php-phpcs. When I run flycheck-next-error, I get 'No more Flycheck errors.'

I have verified this by running Emacs -Q and only requiring the php-mode and flycheck packages.

However, if I run C-c ! C-c php-phpcs (run syntax checker as compile command) I get the proper phpcs output output:

https://gist.github.com/dhaley/645fde60cb730396d393

What could be the cause of the syntax checker not running on the buffer. Let me know what other info I can provide. Here are a few other of my settings:

% phpcs --version PHP_CodeSniffer version 2.0.0RC5 (beta) by Squiz (http://www.squiz.net)

% phpcs -i The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz and Zend

I have 80 errors in my file if I run eslint from the command line. I tested with a smaller file (with less errors) and it was fine. Emacs has 0% cpu usage and I don't see eslint in the process manager. I think it's related to eslint since the file opens if I remove eslint from my PATH.

There's nothing in the message buffer.

GNU Emacs 24.5.1 (x86_64-w64-mingw32) of 2015-05-16 on KAEL

This PR adds a syntax checker for CHICKEN Scheme.

It uses csc to check for syntax errors, and report them accordingly via Flycheck. I followed the example of the Racket checker, meaning Geiser must be running with CHICKEN Scheme implementation for this syntax checker to work.

This is my first (and I hope not last!) contribution to Flycheck, so please do feel free to point out mistakes or any improvements I need to fix.

I wrote a flycheck checker for erlang projects using rebar3, but when I tried adding it to melpa, they said it was pretty basic, so I should try including it in flycheck, so here I am :D

As per the suggestion here: https://github.com/melpa/melpa/pull/4342

These changes should enable the css-stylelint checker in css-mode and scss-mode.

It covers 3 different scenarios:

1) Normal errors and warnings

# .stylelintrc.yaml
rules:
  string-quotes: double
  indentation: [2, { "warn": true }]

/* style.css */
h1 {
  color: 'red'; /* error: single quote */
    margin: 0 auto; /* warning: wrong intentation */
}

stylelint output (missing error level information):

$ stylelint style.css
2:10    Expected double quotes (string-quotes)
3:5 Expected indentation of 2 spaces (indentation)

That's why I used the JSON formatter and wrote my own :error-parser

$ stylelint --formatter json style.css
[{"source":"style.css","deprecations":[],"errored":true,"warnings":[{"line":2,"column":10,"rule":"string-quotes","severity":"error","text":"Expected double quotes (string-quotes)"},{"line":3,"column":5,"rule":"indentation","severity":"warning","text":"Expected indentation of 2 spaces (indentation)"}]}]

2) Syntax errors

/* style.css */
h1 {
  color: 'red; /* syntax error: Unclosed quote */
    margin: 0 auto;
}

$ stylelint --formatter json style.css
CssSyntaxError: style.css:2:10: Unclosed quote

3) Configuration errors

# .stylelintrc.yaml
# should be rules instead of rles
rles:
  string-quotes: double
  indentation: [2, { "warn": true }]

$ stylelint --formatter json style.css
Error: No rules found within configuration. Have you provided a "rules" property?

The :error-filter function adds a line (line number 1) to these errors to be able to show them.

Questions

• What is the best way to define this checker for css-mode and scss-mode?
• What is the best way to use a combination of an :error-parser and some form of :error-patterns?
• Is it necessary to show the Syntax errors and Configuration Errors or should flycheck just fail if these happen?
• Should I rather try to create a PR at stylelint that changes their text formatter to output the error level and then create a simple checker that just uses :error-patterns for all 3 scenarios?

Edit: Connects to #785

This pull request addresses #1297. It does not yet include documentation and tests, since I would first like to ask if there are any technical problems with the patch.

In particular, we may not want to introduce a dependency on switch-buffer-functions, and instead implement that functionality ourselves (it is only about 20 lines of code).

This PR adds support for the Elixir language (as discussed in #877). This relies on dogma for syntax checking, and so does not execute the code being checked as elixirc would.

Edit (@lunaryorn): Connects to #877

TODO:

• [x] ~~Add predicate to make sure checker is not loaded when mix dogma is not available.~~
• [x] Parse dogma's JSON output format.
• [x] Tests for JSON parsing

This is a first iteration of trying to implement #312. It give the possibility to add :cwd to the flycheck-define-checker. :cwd can be a fixed path or a function that returns a absolute path. The function is called just before the checker. The default-directory is only changed in the lexical environment of the checker execution. In addition there is a :environment property, where one can define additional environment variables. ie ("var1=value1" "var2=value2")

Edit: Connects to #312

Flycheck does a great job of staying out of your way while typing, waiting for a save or newline to start complaining.

However, when issuing commands that make several changes to the buffer, it triggers a check inbetween functions. This results in errors reported in valid buffers.

I recorded a demonstration here: http://ascii.io/a/3202

Adding a (let (flycheck-mode)) around the command resolves this issue, but only for one command at a time.

Hey. I'm trying to write custom generic flycheck checker that works with eglot language server package, as it itself is tied to flymake and its author won't do it himself. I've manually unhardcoded flymake calls in eglot in my local elpa directory (for now) and then ended up with the following code in my init.el:

(use-package flycheck
  :ensure t
  :init (global-flycheck-mode))

(use-package eglot
  :ensure t
  :config
  (defun my/start-eglot-flycheck (checker callback)
    (defun my/point->line-col (buffer beg)
      (with-current-buffer buffer
        (save-excursion
          (goto-char beg)
          (cons (line-number-at-pos)
                (- (point)
                   (line-beginning-position))))))
    (defun my/flymake-diagnostic->flycheck-error (diag)
      (pcase-let* ((msg (flymake-diagnostic-text diag))
                   (beg (flymake-diagnostic-beg diag))
                   (buffer (flymake-diagnostic-buffer diag))
                   (`(,line . ,col) (my/point->line-col buffer beg)))
        (flycheck-error-new-at
         line col
         (pcase (flymake-diagnostic-type diag)
           ('eglot-error 'error)
           ('eglot-warning 'warning)
           ('eglot-note 'info))
         msg
         :checker checker)))
    (eglot-flymake-backend
     (lambda (report-action &key region)
         (funcall
          callback 'finished
          (mapcar
           #'my/flymake-diagnostic->flycheck-error
           report-action)))))
  (flycheck-define-generic-checker 'eglot
    "A generic eglot flycheck checker"
    :start #'my/start-eglot-flycheck
    :modes '(python-mode))
  (add-to-list 'flycheck-checkers 'eglot)
  (add-to-list 'flycheck-disabled-checkers 'python-flake8)
  (add-to-list 'flycheck-disabled-checkers 'python-pylint)
  (add-to-list 'flycheck-disabled-checkers 'python-pycompile)
  :hook
  (python-mode . eglot-ensure))

It seems to work all right, I can see error messages from language server in the buffer and error counter on the modeline, but there's one problem. I figured it happens when I type anything in buffer while flycheck (seemingly) is running my custom checker. The problem is that in that situation flycheck somehow gets stuck, error count in the modeline is displayed as "???" (I'm using spaceline to display flycheck error count at the modeline), and M-x flycheck-list-errors displays empty error list even though there are errors displayed in the buffer. I'm not that much of an elisp hacker, so I suppose there's something wrong in my code. Would you please point me at what could be wrong? Does callback passed to :start function require some sort of synchronization or locking?

Here's additional info:

• M-x flycheck-verify-setup

Syntax checkers for buffer models.py in python-mode:

First checker to run:

  eglot
    - may enable: yes

Checkers that are compatible with this mode, but will not run until properly configured:

  python-flake8 (disabled)
    - may enable:         Automatically disabled!
    - executable:         Found at /home/lock/.pyenv/shims/python
    - configuration file: Not found
    - `flake8' module:    Found at "/usr/lib64/python3.6/site-packages/flake8/__init__.py"

  python-pylint (disabled)
    - may enable:         Automatically disabled!
    - executable:         Found at /home/lock/.pyenv/shims/python
    - configuration file: Not found
    - `pylint' module:    Found at "/usr/lib64/python3.6/site-packages/pylint/__init__.py"

  python-pycompile (disabled)
    - may enable: Automatically disabled!
    - executable: Found at /home/lock/.pyenv/shims/python

  python-mypy (disabled)
    - may enable:         Automatically disabled!
    - predicate:          t
    - executable:         Not found
    - configuration file: Not found
    - next checkers:      python-flake8

Flycheck Mode is enabled.  Use M-x universal-argument C-c ! x to
enable disabled checkers.

--------------------

Flycheck version: 32snapshot (package: 20190619.1410)
Emacs version:    26.1
System:           x86_64-pc-linux-gnu
Window system:    x

• My OS: Gentoo stable 64-bit
• M-x emacs-version: GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu) of 2018-09-29
• M-x flycheck-version: Flycheck version: 32snapshot (package: 20190619.1410)

Thanks in advance.

This implements the feature requested in #966 and laid out in https://github.com/flycheck/flycheck/pull/970#issuecomment-219734788.

Now:

• There's a new column in the error list, called File.

  +  [("File" 6)
  

• We don't discard errors that don't match the current filename (in flycheck-relevant-error-p):

  -       (or (not file-name) (flycheck-same-files-p file-name (buffer-file-name)))
  

• We only add overlays for the current buffer in flycheck-add-overlay:

  +  (when (eq (flycheck-error-buffer err) (current-buffer))
  

• In flycheck-next-error-function, when there are no more errors in the current buffer, we jump to the first error from another file.

• The flycheck-error-list-goto-error function uses the same function as the previous item, both use a new function flycheck-jump-to-error.

• We add a new face for filenames, flycheck-error-list-filename, derived from buffer-menu-buffer.

I don't think this is an automatic merge, but it's a straight-forward one. I tried rebasing against master and it worked, but I was unable to get master to load in my Emacs due to a variety of new dependencies which have been added since I last updated flycheck. 😱 So I don't know if it actually runs on your version. Sorry!

Anyway, against 778493e from 9 months ago it works fine. 🙊 I have to work on other things related to Intero now, but I hope this makes it upstream.

Edit (@lunaryorn): Connects to #966

I can't get the markdown-markdown-cli checker working. It seems like flycheck finds the linter, runs it as I'd expect, but then may have some kind of issue interpreting the output. I've read the troubleshooting guide and provided all the debug output below. Any help is appreciated.

🙏 Thank you so much for working on flycheck, I love it!

Error

I'm attempting to use the markdown-markdown-cli checker, but it's giving this error:

Suspicious state from syntax checker markdown-markdownlint-cli: Flycheck checker markdown-markdownlint-cli returned 1, but its output contained no errors: /Users/standefer/.config/yarn/global/node_modules/ignore/index.js:379
  throw new Ctor(message)
  ^

RangeError: path should be a `path.relative()`d string, but got "../../../../var/folders/bh/c53gkgbj7498ds7c4cn2l0840000gq/T/flycheckh0hWzp/CHANGELOG.md"
    at throwError (/Users/standefer/.config/yarn/global/node_modules/ignore/index.js:379:9)
    at checkPath (/Users/standefer/.config/yarn/global/node_modules/ignore/index.js:398:12)
    at Ignore._test (/Users/standefer/.config/yarn/global/node_modules/ignore/index.js:519:5)
    at Ignore.ignores (/Users/standefer/.config/yarn/global/node_modules/ignore/index.js:564:17)
    at ignoreFilter (/Users/standefer/.config/yarn/global/node_modules/markdownlint-cli/markdownlint.js:252:46)
    at /Users/standefer/.config/yarn/global/node_modules/markdownlint-cli/markdownlint.js:255:81
    at Array.filter (<anonymous>)
    at Object.<anonymous> (/Users/standefer/.config/yarn/global/node_modules/markdownlint-cli/markdownlint.js:255:65)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)

M-x flycheck-verify-setup

First checker to run:

  markdown-markdownlint-cli
    - may enable:         yes
    - executable:         Found at /usr/local/bin/markdownlint
    - configuration file: Not found

Checkers that are compatible with this mode, but will not run until properly configured:

  markdown-mdl (automatically disabled) reset
    - may enable:         no
    - executable:         Not found
    - configuration file: Not found

  proselint (automatically disabled) reset
    - may enable: no
    - executable: Not found

  textlint (automatically disabled) reset
    - may enable:         no
    - executable:         Not found
    - configuration file: Not found
    - textlint plugin:    @textlint/markdown

Flycheck Mode is enabled. Use C-u C-c ! x to enable disabled checkers.

--------------------

Flycheck version: 33snapshot (package: 20221213.107)
Emacs version:    28.2
System:           x86_64-apple-darwin18.7.0
Window system:    ns

markdownlint-cli version

$ /usr/local/bin/markdownlint --version
0.32.2

M-x flycheck-compile

The linter errors with CHANGELOG.md are what I'd expect given the state of my code.

-*- mode: compilation; default-directory: "~/code/tesla/" -*-
Compilation started at Wed Dec 21 16:04:31

/usr/local/bin/markdownlint /Users/standefer/code/tesla/CHANGELOG.md
/Users/standefer/code/tesla/CHANGELOG.md:28 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]
/Users/standefer/code/tesla/CHANGELOG.md:29 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 3]
/Users/standefer/code/tesla/CHANGELOG.md:30 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 4]
/Users/standefer/code/tesla/CHANGELOG.md:31 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 5]

Compilation exited abnormally with code 1 at Wed Dec 21 16:04:31

Emacs version

GNU Emacs for Mac OS X - Version 28.2

M-x emacs-version gives:

GNU Emacs 28.2 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 Version 10.14.6 (Build 18G95)) of 2022-09-12

Hello @all

since 2017 I am the owner of the flycheck.org domain (see #1257).

I am not really involved in flycheck development anymore and not at all up-to-date of what is going on in the project. Therefore I would like to pass on the baton to someone else (or a foundation etc.). The domain is registered until Nov 19th 2023 so there should be plenty of time to find a solution.

best regards

Hi,

Currently, if there is an error at the current point of the current buffer, Flycheck will always display it after finishing syntax checking.

I'm using flycheck-posframe and it is quite inconvenient when the popup window automatically displays and hides the current text (when the error message spans several lines).

So, I introduced an option flycheck-display-errors-at-point-after-checking in this PR. When it is set to nil, Flycheck will not automatically display the error after finishing syntax checking.

Can you take a look at this PR and merge it if possible?

Thanks!

I'm missing a way to specify the executable of a command for a specific checker in my case the D checker. I would like to be able to switch between dmd and ldmd2.

As consequence of this I have to maintain to versions of my version of the D checker one; using dmd and one using ldmd2. This is not scalable.

I was looking into https://github.com/flycheck/flycheck/issues/1974 and trying to understand how the python checkers were implemented

Looking at the code, I see that flake8 and pylint are called using python -m and using the stdin option when enabled. But mypy is called directly as is.

Is there any reasoning for this? I looked through the issue https://github.com/flycheck/flycheck/issues/1055 but I am still not clear on what advantage you might get by using python -m over just calling the flake8 executable directly?

@cpitclaudel I would appreciate if you can shed some light on this.

Hi,

I'm getting the following whenever flycheck runs on .el files..

I'm on emacs 28, on windows.

Is there a way to make it go away? :)

Thanks!

Suspicious state from syntax checker emacs-lisp: Flycheck checker emacs-lisp returned 255, but its output contained no errors: Debugger entered--Lisp error: (end-of-file)
  command-line-1(("--directory" "c:/Users/Jonathan/.doom.d/snippets/" "--directory" "c:/Users/Jonathan/.emacs.d/orgnv/" "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." "--directory" "c:/Users/Jonathan/.emacs.d/.local/straight/build-2..." ...))
  command-line()
  normal-top-level()

Suspicious state from syntax checker emacs-lisp: Flycheck checker emacs-lisp returned 255, but its output contained no errors: Debugger entered--Lisp error: (end-of-file)