Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Nick Mavis
@nickmavis_twitter
everything it shows seems to indicate it's working
Originally my actual checker was giving me an abnormal exit in flycheck-cimpile because I was calling exit(1) on errors to kill rulecritic
but I changed it to 0 to exit a little more gracefully for flycheck
fmdkdd
@fmdkdd
Actually flycheck expects a non-zero exit code when there are errors to be parsed
But a zero exit code with errors should still work
(but explains why you didn't get a warning from Flycheck when the exit code is 1, but no errors could be found)
Nick Mavis
@nickmavis_twitter
interesting. I just wanted to be sure that it wasn't interfering since it gave me an abnormal exit message after my error in flycheck-compile
I thought it was a good debugging step at least
fmdkdd
@fmdkdd
Well, I'm out of ideas
if you can reproduce on a stock emacs with minimal configuration (although including Flycheck, of course), please do open up an issue
Nick Mavis
@nickmavis_twitter
Found 1 new package(s) to install...
--> refreshing package archive: gnu... [3/3]
--> installing package: flycheck-snort@snort... [1/1]
Package flycheck-snort is unavailable. Is the package name misspelled?
on boot
might be a bad sign
although it's registered as a checker?
fmdkdd
@fmdkdd
use-package will pull the package from ELPA by default, but your checker is only local for now, right?
Nick Mavis
@nickmavis_twitter
yup
fmdkdd
@fmdkdd
You want to pass the load-path:
(use-package flycheck-snort
  :load-path "~/path/to/flycheck-snort/folder/"
  ...
Nick Mavis
@nickmavis_twitter
(require 'flycheck-snort "<path>/flycheck-snort/flycheck-snort")
is how I initialized it in my user-init
but I have this as well in my packages.el for the layer
   (flycheck-snort :toggle (configuration-layer/package-usedp 'flycheck))
fmdkdd
@fmdkdd
I don't know the Spacemacs specifics
Nick Mavis
@nickmavis_twitter
under (setq snort-packages '(
no worries. I'll keep fiddling with it. Thanks for your help
Brandon Verkamp
@brandon58_gitlab
Hey all, I'm working with the ESP-IDF for the ESP32 and I'm trying to make flycheck aware of its include directories. The structure is pretty strange, all of the headers are in subdirectories of the components directory and each of /those/ directories has its own include subdirectory. If I just point flycheck-gcc-include-path at components in the IDF directory will it pick up on all the nested include directories, or do I need to manually add each?
Brandon Verkamp
@brandon58_gitlab
Update: This solution does not work
fmdkdd
@fmdkdd
Probably you need a bit of elisp to list the directories under components and add them all to flycheck-gcc-include-path
Brandon Verkamp
@brandon58_gitlab
I suppose I'll have to do so. At first I just used find to list all the include directories and piped the output to be used in .dir-locals.el, but I'm finding out now that a lot of these components also rely on headers in their components folder outside of the include directory... Well, it's an excuse to learn some elisp on the job I suppose.
fmdkdd
@fmdkdd
Good perspective ;) Also, there may be Flycheck extensions that ease the management of includes, but this case seems rather specific.
Boris
@d12frosted_gitlab
Hi everyone! Sorry if this question was asked and answered multiple times, I could find any information that would help me. So I am writing a custom checker and everything is fine, but I have one situation when I don't have a line number for the error and I would like to show it on the first line of the file. E.g. usually my errors are in the format FILENAME:LINE:COLUMN MESSAGE, but this particular error is FILENAME: MESSAGE. I am using error-patterns and have it set to the following:
     (error line-start (file-name) ":" line ":" column ": " (message) line-end)
     (error line-start (file-name) ": " (message) line-end)
This message was deleted
But instead of showing me the error I see nothing in the buffer and in the list of errors associated with the buffer.
I am using Emacs 27.0.50 and flycheck-20190619.1410
Boris
@d12frosted_gitlab
If I remove the last pattern I at least see the error about suspicious state, but with that pattern flycheck tells me that everything is fine.
fmdkdd
@fmdkdd
@d12frosted_gitlab Errors without a line number will be discarded by flycheck-relevant-error-p. You want to set the :error-filter to flycheck-fill-empty-line-numbers (or something custom)
Boris
@d12frosted_gitlab
@fmdkdd ok, that worked! Thank you so much!
9m9
@9m9

Hello, I use the latest version of flycheck with go version 1.12.6. But I get errors

Suspicious state from syntax checker go-vet: Flycheck checker go-vet returned non-zero exit code 1, but its output contained no errors: vet: invoking "go tool vet" directly is unsupported; use "go vet"
exit status 1

Try installing a more recent version of go-vet, and please open a bug report if the issue persists in the latest release.  Thanks!

How to solve that? Thanks in advance!

my golang version: go version go1.12.6 linux/amd64
my flycheck version: 20190709.1443
9m9
@9m9
图片.png
problem solved. I have to set those variables manually.
Paul Davis
@paulbdavis
Are there any plans to do a release on melpa-stable any time soon? It's been nearly two years since the last tagged release
fmdkdd
@fmdkdd
@paulbdavis there are! We'd like to find a way to include #1400 in it. As always, free time is the bottleneck here
Andres Moreno
@andres-moreno

I am trying to use ESLint with Flycheck.

  1. ESLint works from the command line so if I type eslint <filename> , it does its thing and changes in the config file are reflected in the output (e.g., changing the spacing)
  2. I have an .eslintrc.json file at the root of my project
  3. flycheck-verify-setup tells me that my config file is "missing or incorrect"

Flycheck: 32snapshot (package: 20190213.1525)
Emacs version: 27.0.50
System: x86_64-pc-linux-gnu

Any suggestions would be greatly appreciated!

Andres Moreno
@andres-moreno
The issue above is a known bug: flycheck/flycheck#1607
fmdkdd
@fmdkdd
@andres-moreno should be fixed in latest MELPA version
Andres Moreno
@andres-moreno
@fmdkdd Thanks! For the time being I am using ESLint 5.15.3 with no issues--flycheck is great!
fmdkdd
@fmdkdd
@andres-moreno Glad to hear! Happy hacking ;)
Gustavo Rivas
@Griger
Hi, I like flycheck a lot. However I have found a problem, flymake. This minor-mode is also activated in my buffers by default, so for example, I have problems configuring pylint. Because flycheck does not lint some errors that I disable in my .pylintrc file, but flymake does. I am trying to disable flymake globally by default in my init.el, but I am not able to do this by for example do (add-hook 'prog-mode-hook (lambda () (flymake-mode -1)), or even using the obsolete function flymake-mode-off.
fmdkdd
@fmdkdd
@Griger Maybe it would be easier to turn it on only in the buffers you want it (e.g., python buffers) rather than have it default and turn it off globally?