Fixes: bug#31738
* doc/misc/flymake.texi (Using Flymake, Customizable variables):
Mention flymake-start-on-save-buffer.
* etc/NEWS: Mention flymake-start-on-save-buffer.
@code{flymake-mode} is started, unless
@code{flymake-start-on-flymake-mode} is nil;
+@item
+the buffer is saved, unless @code{flymake-start-on-save-buffer} is
+nil;
+
@item
a newline character is added to the buffer, unless
@code{flymake-start-syntax-check-on-newline} is nil;
A boolean flag indicating whether to start syntax check immediately
after enabling @code{flymake-mode}.
+@item flymake-start-on-save-buffer
+A boolean flag indicating whether to start syntax check after saving
+the buffer.
+
@item flymake-error
A custom face for highlighting regions for which an error has been
reported.
You should instead set properties on known diagnostic symbols, like
':error' and ':warning', as demonstrated in the Flymake manual.
+*** New customizable variable 'flymake-start-on-save-buffer'
+Control whether Flymake starts checking the buffer on save.
+
** Package
*** New 'package-quickstart' feature
When 'package-quickstart' is non-nil, package.el precomputes a big autoloads