Did you check docs and existing issues?

• I have read all the LazyVim docs
• I have searched the existing issues of LazyVim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.2

Operating system/version

Fedora Linux 38

Describe the bug

I don't use lualine and rely on the native statusline instead, however the change introduced in This recent commit resets the laststatus option in the alpha-nvim config function. Therefore, my setting (vim.o.laststatus = 2) from the options.lua file gets overriden when as soon as that function runs.

So far my workaround has been to copy-paste the config function an remove the offending line, but I feel like there should be a better solution.

In any case, I feel it might be bad practice to change a global setting from a plugin's config function as that can easily lead to unexpected behavior.

Steps To Reproduce

1. vim.o.laststatus = 2 in options.lua
2. start nvim with alpha-nvim enabled and lualine disabled

Expected Behavior

The custom value set in the options.lua file should not be overwritten.

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {"folke/LazyVim", import= "lazyvim.plugins"},
{{"nvim-lualine/lualine.nvim", enabled = false}},
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
vim.opt.laststatus = 2