v1.3.1

This minor version focuses on excluding the next lsp clients by default.

Minor fixes

• marksman: It would display a warning message on restating the client.
• lua_lsp: Selene would not apply selene.toml correctly on restarting the client

v1.3.0

Breaking changes

This version drops support for Neovim 0.9.

• To keep using this plugin please download Neovim 0.10 .
• Or alternatively lock your garbage-day version to v1.2.0, which is the latest version to support Neovim 0.9.

v1.2.0

New features

• aggressive_mode_ignore new option to ignore buffers on aggressive_mode.

Minor fixes

• aggresive_mode won't trigger on UI buffers by default anymore (neotree, aerial, etc).
• aggresive_mode won't trigger on note taking buffers by default anymore (markdown, txt, latex, etc).

Development notes

Thanks to @niksingh710 for proposing this improvement.

v1.1.0

This version include fixes to make aggressive mode more reliable

Minor fixes

• aggressive mode Now trigger garbage collection reliably.
• opts.timeout: Default value is 1000ms instead of 100ms now to ensure slower LSP clients like clang reload correctly.

1.0.9

New features

• wakeup_delay new option to avoid waking up neovim by accident when passing the mouse over it. Wait an amount of ms before resuming LSP after the mouse re-enters nvim. If the mouse leaves nvim before the wakeup_delay ends, then wakeup is canceled.

1.0.8

New features

• timeout is a new option that allows to configure the total amount of ms the option retries is gonna take to complete.

Minor fixes

• aggressive_mode: has been improved. If enabled, when entering a buffer, if the filetype of the new buffer is the same as the previous buffer, don't stop LSP. In practice this makes possible to keep LSP enabled while editing files of the same filetype side to side on aggressive mode.
• We now blacklist null-ls by default because stopping it save no resources, and it makes the user experience less snappy. But it works fine if the user prefers to enable it.

Development notes

• This version represents the final product and it should be extraordinarily stable.

1.0.7

Breaking changes

• aggressive_mode is the new option in replacement for stop_invisible.

New features

• retries new option to specify the number of times to try to restore LSP clients. Useful if one of your clients is slow to respond.
• Now garbage-day.nvim is compatible with null-ls.

Development notes

Manually keeping track of the stopped LSP clients has been nightmare fuel during this couple days of development. Mostly due to the fact lsp.get_clients() don't always tell the truth. To solve this, we now rely on lsp-config instead. Now that we don't need to manually keep track of the stopped clients, code is much simpler.

This version should be about 100% stable.

v1.0.6

Breaking changes

• excluded_filetypes option has been removed. Please use excluded_lsp_clients instead, which offers better control.

More info

• This version is mostly a cleanup of v1.0.5.
• At this point things should be pretty stable out of the box.

v1.0.5

Minor fixes

• null-ls is now ignored by default.

New features

• ignored_lsp_clients this new option allow users to ignore some particular lsp clients, so they are never stopped.
• vim.g.garbage_day_config We now expose this global that allow changing options on the fly.

More info

• Unlike normal lsp clients, null-ls was not designed to be stopped, and doing so would cause it to malfunction.
• Due to the fact null-ls is just one single lsp server attached to all buffers, and it doesn't run any program in background, but instead it just send system calls to parsers, the amount of resources liberated from stopping it would be negligible anyway.

v1.0.4

This version focuses on simplifying the code, to make the project easier to fork and contribute.