Closed ajayd-san closed 1 year ago
packercompile
@default-303 I set it up by placing header inside config
as:
require('dashboard').setup({
theme = 'hyper',
config = {
header = banner,
}
})
You keep telling everyone to compile but don’t put in docs.
why i need put it in doc ? it is packer usage ? why you don't read packer doc? i think packer doc had tell you when you need sync or compile ?
Users are expecting their config to be picked up like most configs. I don’t remember last time I had to sync or compile for config change besides trying dashboard. That’s why people keep saying these things. They expect it.
I’m guessing it’s the way dashboard is setup to be more efficient. But I don’t think that is obvious to casual user.
you know how packer works ? it generate a compile file and load it. it include all your plugins loaded rule and config. if you changed any plugins config you must to sync or compile. not issue of dashboard. if you don't like this way change to lazy.nvim it no need you to compile or sync. it use lua package loaders way to load lua plugins.
Describe the bug I'm try to set a custom header but it does not reflect when I restart nvim. I'm using
hyper
and tried setting the ascii art in my config. It does not seem to work.Config
in after/plugin/dashboard.lua
in lua/default/packer.lua:
Expected behavior The plugin displays the custom header as set in its config.