bug#34294: 27.0.50; flymake-start-on-save-buffer has no effect

[João Távora]

On Sat, Feb 2, 2019 at 9:33 PM Juri Linkov <juri@linkov.net> wrote:
>
> X-Debbugs-CC: João Távora <joaotavora@gmail.com>
>
> I have flymake-start-on-save-buffer customized to 't' to check syntax
> only when a buffer is saved, but it still checks the unfinished work
> while edits are in progress, showing the errors that make no sense
> until the buffer is saved

They "make sense" if you were to interpret/compile the buffer's
contents at that moment.  It's called fly-make for a reason ;-).

> , even when flymake-start-syntax-check-on-newline
> and flymake-start-on-flymake-mode are nil.
> Is it possible to customize flymake to kick in only on saving?

You can set flymake-no-changes-timeout to nil. See its docstring.

If that works, you can probably close this bug.

-- 
João Távora