Recent changes to bugs

bug in flymake-can-syntax-check-file hit when using vc commands

Emin Martinian — Thu, 21 Aug 2014 16:06:52 -0000

I think there is a bug in the flymake-can-syntax-check-file function. I think the line that reads
(if (flymake-get-init-function file-name) t nil))
should be changed to:
(if (and file-name (flymake-get-init-function file-name)) t nil))

That is, if file-name is nil then don't do anything else.

The effect of the existing bug is that when I do version control commands (like check-in a file) I get an Invalid file-name error.

Thanks.

Error opening file inside directory with space in name.

kost bebix — Sun, 08 Apr 2012 16:51:33 -0000

Hi! I don't know ELisp, so couldn't fix the bug. It happens when I try to open file ~/Ubuntu\ One/playground/learnc/ex19.h, flymake says "Configuration error occured ..."

I think the problem is inside this function:

(defun flymake-get-make-cmdline (source base-dir)
(list "make"
(list "-s"
"-C"
base-dir
(concat "CHK_SOURCES=" source)
"SYNTAX_CHECK_MODE=1"
"check-syntax")))

I tried to change it to

(defun flymake-get-make-cmdline (source base-dir)
(list "make"
(list "-s"
"-C"
(shell-quote-argument base-dir)
(concat "CHK_SOURCES=" (shell-quote-argument source))
"SYNTAX_CHECK_MODE=1"
"check-syntax")))

But that didn't help (it now prints "make ..." command right and if I copy-paste it to shell it will work fine, but still flymake reports about it as error).

flymake-err-line-patterns not uniform

Jochen T. — Thu, 02 Dec 2010 14:08:08 -0000

flymake-err-line-patterns includes compilation-error-regexp-alist, which has (now) a different structure

while flymake-err-line-patterns is:
(regexp file-idx line-idx col-idx err-text-idx)
t is:
software-identifier
compilation-error-regexp-alist-alist looks more similar but is still different ...
(software-identifier regexp file-idx line-idx ? ?)

this leads to an error, if none flymake.el's patterns matches and the first entry of compilation... "absoft" is used, which is no list and therefore stops flymake when no error occurs on (for example) a php syntax-check. (which replies with: No syntax errors detected in [filename])

a temporary fix is to remove compilation... from the list

colorgcc compatibility

giurrero — Mon, 22 Nov 2010 17:14:02 -0000

flymake doesn't work with colorgcc (http://schlueters.de/colorgcc.html). See an example here: http://stackoverflow.com/questions/4149995/flymake-cfgerr-problem

ZIP file does not use standard package-NN.NN directory

Jari Aalto — Wed, 31 Mar 2004 22:21:52 -0000

Kindly package the release so that it uses standard
version naming scheme:

flymake-0.2/

Instead of now unpacking to

flymake/

This will help upgrading and overall maintenance of
many packages.

Error reported for the last line are lost

Pavel Kobiakov — Thu, 15 Jan 2004 07:30:02 -0000

In case syntax check tool reports errors for both the
last line of the file and for the next line, only first set of
errors is displayed in error menu for the last line.