If Flymake has highlighted the buffer, you may hover the mouse on the
highlighted regions to learn what the specific problem
is. Alternatively, place point on the highlighted regions and use the
If the diagnostics are outside the visible region of the buffer,
let you navigate to the next/previous erroneous regions,
respectively. It might be a good idea to map them to M-n and
flymake-mode, by adding to your init file:
(define-key flymake-mode-map (kbd "M-n") 'flymake-goto-next-error) (define-key flymake-mode-map (kbd "M-p") 'flymake-goto-prev-error)
Sometimes it is useful to have a detailed overview of the diagnostics
in your files without having to jump to each one. The commands
flymake-show-project-diagnostics are designed to handle this
situation. When invoked, they bring up a separate buffer containing a
detailed structured listing of multiple diagnostics in the current
buffer or for the current project, respectively (see Projects in The Emacs Editor).
The listings is continuously updated as you edit source code, adding or removing lines as you make or correct mistakes. Each line of this listing includes the type of the diagnostic, its line and column in the file, as well as the diagnostic message. You may sort the listing by each of these columns.