https://github.com/NvChad/NvChad/blob/v2.5/lua/nvchad/options.lua#L12

you should add it here

https://github.com/NvChad/NvChad/blob/v2.5/lua/nvchad/options.lua#L12

you should add it here

Unfortunately, if the user decides to change the clipboard option in his own lua/options.lua, there is no way to reset and defer the option.

-- User options.lua in "NvChad/starter":

require "nvchad.options"
-- add yours here!

local o = vim.o
-- o.cursorlineopt ='both' -- to enable cursorline!

-- Not deferred!
o.clipboard = "unnamed" -- or a custom clipboard tool config, see ":h g:clipboard"

-- Nvchad options.lua in "NvChad/NvChad":

vim.schedule(function()
  o.clipboard = "unnamedplus" -- overrides user's changes...
end)

I also tried the approach in an autocommand on LazyLoad, added as the first statement to lua/nvchad/plugins/init.lua. That did not improve the performance, probably kicked in too late.

EDIT: An example of "doing something" with spec.config supplied by the user can be found here

ig its better to remove the cliboard function from main repo itself and let the user add it in his starter..

I dont get why such simple option should be heavy, i hope its not cuz of windows 😨 😡

ig its better to remove the cliboard function from main repo itself and let the user add it in his starter..

Yes, that would be the best option. I think that existing users would not profit though.

I dont get why such simple option should be heavy, i hope its not cuz of windows 😨 😡

That's discussed here. It can happen on linux("xsel"), macos("pbcopy") and windows-wsl2, as far as I can see.

Would you like me to propose a PR on the starter?

what if the main nvchad's repo's option file had just this?

vim.schedule(function()
  o.clipboard = "unnamedplus" -- overrides user's changes...
end)

That would work except when the user adds his own clipboard setting to lua/options.lua. The user could decide to opt-out (""), or change ("unnamed" for example) or provide a completely custom config according to :h g:clipboard. As the default vim.o.clipboard option also has the empty string as value, it is not trivial to distinguish between user-changes and that default.

The problem, I think, is that in the starter, in NvChad's config function, lua/options.lua is required. The effect is that the loading of the options is "in control" by the user, not by NvChad.

That's why I ended up with decorating that config function, taking back control. I think that works in 99.99% of the cases. However, because the user is free to put any code he desires inside the config function, the "timing" could still break. Highly unlikely in my opinion.

@siduck,

I found a better approach and pushed a new commit. I used the local lua/options.lua to test:

1. No override
2. o.clipboard = ""
3. `o.clipboard = "unnamed"
4. vim.opt.clipboard = ""

The code now uses an autocommand on LazyDone: "when lazy has finished starting up and loaded your config"

@abeldekat the user can add his own vim.schedule... in his options file

Yes, the user can do:

o.clipboard = "" -- reset
vim.schedule(function()
  o.clipboard = "unnamedplus"
end)