Q: How to manually trigger LSP garbage collection in Neovim with this plugin?

Use the provided utility functions: require('garbage-day.utils').stop_lsp() to stop all LSP clients and require('garbage-day.utils').start_lsp() to restart them for the current buffer, as explained in the FAQ for manual control.

Q: What should I do if garbage-day.nvim doesn't work on Neovim 0.12 or higher?

The plugin is only tested for Neovim 0.10 and 0.11. If you're on a superior version and encounter issues, open a GitHub issue tagging the author, as mentioned in the FAQ, but there's no guarantee of immediate fixes.

Q: Can I exclude specific LSP clients from being stopped by garbage-day.nvim?

Yes, use the excluded_lsp_clients option to list LSP clients that should never be stopped, which is useful for those that misbehave when restarted, with a default list provided in the config file.

Q: What are the best settings for aggressive mode in garbage-day.nvim?

Aggressive mode maximizes RAM savings by stopping all LSP clients except the current buffer on entry, but it's best used when you frequently switch buffers with different filetypes and have fast LSP restart times to avoid workflow disruptions.

Q: How to enable debug notifications for LSP garbage collection?

Set the notifications option to true in the configuration to get a notification every time garbage collection triggers, helping you monitor activity, as detailed in the 'Debug options' section of the README.

Question 1

How does garbage-day.nvim compare to lsp-timeout.nvim?

Accepted Answer

garbage-day.nvim is recommended for Neovim 0.10 and above, offering features like aggressive mode and configurable grace periods, while lsp-timeout.nvim is suggested for versions <=0.8 and might be simpler but less feature-rich for newer setups.

Question 2

How to manually trigger LSP garbage collection in Neovim with this plugin?

Accepted Answer

Use the provided utility functions: require('garbage-day.utils').stop_lsp() to stop all LSP clients and require('garbage-day.utils').start_lsp() to restart them for the current buffer, as explained in the FAQ for manual control.

Question 3

What should I do if garbage-day.nvim doesn't work on Neovim 0.12 or higher?

Accepted Answer

The plugin is only tested for Neovim 0.10 and 0.11. If you're on a superior version and encounter issues, open a GitHub issue tagging the author, as mentioned in the FAQ, but there's no guarantee of immediate fixes.

Question 4

Can I exclude specific LSP clients from being stopped by garbage-day.nvim?

Accepted Answer

Yes, use the excluded_lsp_clients option to list LSP clients that should never be stopped, which is useful for those that misbehave when restarted, with a default list provided in the config file.

Question 5

What are the best settings for aggressive mode in garbage-day.nvim?

Accepted Answer

Aggressive mode maximizes RAM savings by stopping all LSP clients except the current buffer on entry, but it's best used when you frequently switch buffers with different filetypes and have fast LSP restart times to avoid workflow disruptions.

Question 6

How to enable debug notifications for LSP garbage collection?

Accepted Answer

Set the notifications option to true in the configuration to get a notification every time garbage collection triggers, helping you monitor activity, as detailed in the 'Debug options' section of the README.

zeioth/garbage-day.nvim

What is zeioth/garbage-day.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions