Variable: flymake-list-only-diagnostics

flymake-list-only-diagnostics is a variable defined in flymake.el.gz.

Value

nil

Documentation

Diagnostics list meant for listing, not highlighting.

This variable holds an alist ((FILE-NAME . DIAGS) ...) where FILE-NAME is a string holding an absolute file name and DIAGS is a list of diagnostic objects created with flymake-make-diagnostic. These diagnostics are never annotated as overlays in actual buffers: they merely serve as temporary stand-ins for more accurate diagnostics that are produced once the file they refer to is visited and flymake-mode(var)/flymake-mode(fun) is turned on in the resulting buffer.

Flymake backends that somehow gain sporadic information about diagnostics in neighboring files may freely modify this variable by adding or removing entries to for those files. If the information about those neighboring files is acquired repeatedly and reliably, it may be more sensible to report them as
"foreign" diagnostics instead.

Commands such as flymake-show-project-diagnostics will include some of this variable's contents the diagnostic listings.

Source Code

;; Defined in /usr/src/emacs/lisp/progmodes/flymake.el.gz
;;; Per-project diagnostic listing
;;;

(defvar flymake-list-only-diagnostics nil
  "Diagnostics list meant for listing, not highlighting.
This variable holds an alist ((FILE-NAME . DIAGS) ...) where
FILE-NAME is a string holding an absolute file name and DIAGS is
a list of diagnostic objects created with
`flymake-make-diagnostic'.  These diagnostics are never annotated
as overlays in actual buffers: they merely serve as temporary
stand-ins for more accurate diagnostics that are produced once
the file they refer to is visited and `flymake-mode' is turned on
in the resulting buffer.

Flymake backends that somehow gain sporadic information about
diagnostics in neighboring files may freely modify this variable
by adding or removing entries to for those files.  If the
information about those neighboring files is acquired repeatedly
and reliably, it may be more sensible to report them as
\"foreign\" diagnostics instead.

Commands such as `flymake-show-project-diagnostics' will include
some of this variable's contents the diagnostic listings.")