Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • That is strange. With my stock flycheck config, I did M-x flycheck-verify-setup and my emacs-lisp was set to may enable: yes, may run: t. What happens if you do C-u C-c ! x to enable the emacs-lisp checker? Commented Apr 2 at 1:22
  • @g-gundam please see updated question Commented Apr 3 at 7:10
  • It seems like a function called flycheck--emacs-lisp-enabled-p is responsible for the value printed after may run. Can you try putting (flycheck--emacs-lisp-enabled-p) in an elisp file and evaluating it. For me, it returns t but I wonder if it'll be nil for you. Commented Apr 4 at 7:01
  • thanks a lof for looking into this, @g-gundam. apparently this returns t for me, too. Commented Apr 4 at 11:43
  • 1
    @g-gundam, you encouraged me to look into flycheck.el and i have found that the emacs-lisp checker defines a predicate that prevents the checker from beeing run in buffers that are not ment to be byte-compiled and i was in fact in buffer for the "init.el" file, which is not ment to be byte compiled... i think i can close my question :-) Commented Apr 4 at 11:55