Question 1

How do I set up nvim-early-retirement to ignore Python files?

Accepted Answer

Add 'python' to the ignoredFiletypes array in your configuration. For example, set ignoredFiletypes = {"python"} in the opts table to prevent auto-closing of Python buffers.

Question 2

Nvim-early-retirement vs hbac.nvim: which is better for closing inactive buffers?

Accepted Answer

Nvim-early-retirement focuses on time-based inactivity with extensive config options, while hbac.nvim targets unedited files. Choose based on whether you need inactivity timing or edit-status criteria for cleanup.

Question 3

Can I use nvim-early-retirement with session management plugins?

Accepted Answer

Yes, set ignoreUnloadedBufs = true to ignore buffers added by session plugins without loading them. This prevents conflicts with plugins that manage buffer states.

Question 4

How to enable notifications when a buffer is auto-closed?

Accepted Answer

Set notificationOnAutoClose = true in the configuration and ensure a notification plugin like nvim-notify is installed. The plugin will then show alerts on buffer closure.

Question 5

What happens to unsaved changes when a buffer is retired?

Accepted Answer

If ignoreUnsavedChangesBufs is true (default), buffers with unsaved changes are ignored. If false, they are automatically written and closed, which could lead to data loss if not intended.

Question 6

Is nvim-early-retirement compatible with Neovim 0.9?

Accepted Answer

Core features work, but the deleteBufferWhenFileDeleted option requires Neovim ≥0.10. You can use other settings without issue, but file deletion won't function on older versions.

nvim-early-retirement

What is nvim-early-retirement?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions