v5.5.0

Fixed

• The behavior of the compilation directory. The existing behavior was misleading and did not match the documentation or the Emacs plugin behavior. :Compile now uses the current working directory (vim.fn.getcwd()), unless the vim.g.compilation_directory global variable is set (in which case, :Compile unsets it once it's finished compiling); :Recompile now always uses the directory used by the last :Compile.

v5.4.0

Fixed

• Issue with calling the API functions without some optional fields crashing.

v5.3.2

Added

• The CompileDebugError command, which prints debug information about the error under the current line (along with a matching API function).

v5.3.1

Added

• Documentation for minimum supported version of Neovim.

v5.3.0

Changed

• The behavior of the q mapping within the compilation buffer; instead of running <CMD>q<CR> and possibly quitting Neovim, it now runs <CMD>bdelete<CR>, which won't close out the entire editor.
• No longer outputs additional lines created by the process once interrupted/exited.

v5.2.0

Added

• The CompilationFinished autocmd (a pattern of User) which triggers when the compilation is finished.

v5.1.0

Added

• A highlight of the error's locus when jumping to it, along with the error_locus_highlight option to configure if the highlight should occur, and for how long.
• The priority key for error matchers, and a default priority for the default clang_include matcher.
• The :FirstError command, which jumps to the Nth error based on the count (defaulting to 1).

v5.0.2

Fixed

• Issue with completion when using nvim-cmp.

Changed

• The order of the docs.

v5.0.1

Fixed

• Issue with ANSI color sequences not being highlighted correctly by baleia.

v5.0.0

Added

• The ability to use compile-mode features in any buffer with the compilation filetype; this means you can save command outputs in a file and reopen it to go through errors and the like.
• The use_diagnostics configuration option, which will cause Neovim diagnostics to be used instead of opening the compilation buffer to show errors.
• (Breaking) The error_threshold configuration option, which determines what level of errors are considered when jumping/moving between errors (i.e. using :NextError, :CompileNextError, etc.). This defaults to compile_mode.level.WARNING, which means that INFO level errors are no longer considered by default. You can set this option to compile_mode.level.INFO to revert to the old behavior.

Changed

• (Breaking) The behavior when opening a window for compilation; instead of staying in the compilation buffer's window, compiling will now remain in the window where it originally happened. (You should note this in case you have an autocmd that does this behavior manually - it will now have the opposite effect in some cases, so you will likely want to remove it).

Removed

• (Breaking) The setup function has now been completely removed. Instead, configuration should use the vim.g.compile_mode object, which can be given the type CompileModeOpts.