A new option is now available in both vim(9.0.0667) and neovim(0.9) that should replace this plugin. The new 'splitkeep' option offers two new available behaviors.

• set splitkeep=screen keeps the same screen screen lines in all split windows and is the most "stable" to me.
• set splitkeep=topline keeps the same topline as an alternative.

Neovim plugin to stabilize buffer content on window open/close events.

See example comparing default behavior and with stabilize.nvim active:

Install with vim-plug:

Plug 'luukvbaal/stabilize.nvim'callplug#end() lua << EOF require("stabilize").setup() EOF

Install with packer:

use{"luukvbaal/stabilize.nvim", config=function() require("stabilize").setup() end } 

The plugin will stabilize your buffer content on window open/close events after calling require("stabilize").setup().

{force=true, -- stabilize window even when current cursor position will be hidden behind new windowforcemark=nil-- set context mark to register on force event which can be jumped to with '<forcemark>ignore={-- do not manage windows matching these file/buftypesfiletype={"help", "list", "Trouble" }, buftype={"terminal", "quickfix", "loclist" } } nested=nil-- comma-separated list of autocmds that wil trigger the plugins window restore function }

Because autocmds are by default not nested (:h autocmd-nested), windows spawned by autocommands won't trigger the plugins window restore function. To stabilize these window events, a config option nested is exposed which can be used to trigger doautocmd User StabilizeRestore.

For example, to stabilize window events such as opening the quickfix list (or trouble.nvim) on QuickFixCmdPost or DiagnosticChanged events. For neovim >= 0.7, set the nested cfg to(mind the wildcard):

nested = "QuickFixCmdPost,DiagnosticChanged *" 

The plugin keeps track of the number of windows on the current tabpage and will skip restoring the windows if the number of windows hasn't changed since before firing these nested events(performance consideration).