Replies: 1 comment 5 replies
-
Is the filetype being detected properly? It will only trigger for the log filetype if you open a buffer that gets detected as the log filetype You are correct in that optionalPlugins and startupPlugins are not arbitrary, the categories you make within each section are, but the sections you can use are listed here https://nixcats.org/nixCats_format.html#nixCats.flake.outputs.categories startupPlugins goes to The default load hook for |
Beta Was this translation helpful? Give feedback.
-
Hello! Hope you are doing well.
flake.nix
:lua/custom/plugins/init.lua
:lua/custom/plugins/filetypes/vim-log-highlighting/init.lua
:But when I open any log file; the plugin is not activated, i.e., not syntax highlighting is showing. Since it's a vim plugin, there's no sth like below:
One particular thing is that, if I move
pkgs.neovimPlugins.vim-log-highlighting
to thestartupPlugins
set, it just works. But I don't want it to be loaded on startup; I want it to lazy load and work withft = "log"
.So I take that
startupPlugins
andoptionalPlugins
are not just random arbitrary sets? But I checknixCatsUtils
and it does not seem to have hardcode the sets to do something special...Or is it this particular plugin requires special handling? Like it can't be lazy loaded because it needs to detect filetype?
I see that, in the example, if we just include the
vim-*
plugins and without any other handling, they are already available to be used:Any help is much appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions