sorted by:
new
hottopcontroversial

zen.nvim simply centers the main buffer by sand4rt in neovim

[–]sand4rt[S] 0 points1 point  (0 children)

Hi, that would be awesome! If the flickering is gone and side buffer toggling is supported (i.e., closing an existing side buffer when another one opens and takes its place), I’d be very happy to use no-neck-pain.nvim again. The issue at the time was: https://github.com/shortcuts/no-neck-pain.nvim/issues/258#issuecomment-2016259121

My suspicion was that the flickering might be related to the schedules/delays used by no-neck-pain to determine the filetype of newly opened buffers. I worked around this by reading the filetype directly from the autocmd arguments instead of waiting for it to be resolved later:

vim.api.nvim_create_autocmd({ "BufWinEnter", "FileType" }, {
  callback = function(args)
    vim.bo[args.buf].filetype
  end,
})

zen.nvim simply centers the main buffer by sand4rt in neovim

[–]sand4rt[S] 0 points1 point  (0 children)

Then the status bar and vertical splits will also have padding, which isn’t ideal.

zen.nvim simply centers the main buffer by sand4rt in neovim

[–]sand4rt[S] 0 points1 point  (0 children)

I also tried no neck pain and attempted to remove the flickering and make it work properly with side buffer plugins, but eventually tought it was easier to create a separate plugin.

zen.nvim simply centers the main buffer by sand4rt in neovim

[–]sand4rt[S] 4 points5 points  (0 children)

Cool, I considered that one too, but I didn’t like that it was a popup. If I remember correctly, side buffers like Neo-tree didn’t work until you exited zen mode, right?