You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2022. It is now read-only.
I'm thinking about supporting loading order. It's not quite the same as defer since it will allow to source plugins in different order. For example
We have plugins that provide powerline modules, for example langmap.kak and therefore rely on powerline.kak. So if we're going to load plugins we should load powerline before langmap. We can do it like so:
But if there are many plugins in kakrc it gets harder every time to figure out the order and move plugins around is a tedious task. So instead of keeping an order, it could be set with after keyword:
plug "andreyorst/langmap.kak" after "powerline.kak"
plug "andreyorst/powerline.kak"
Not sure how useful this feature will be, but there are some other plugins already that depend on other plugins, for example: kakoune-emmet depends on kakoune-snippets
The text was updated successfully, but these errors were encountered:
I'm thinking about supporting loading order. It's not quite the same as
defer
since it will allow to source plugins in different order. For exampleWe have plugins that provide powerline modules, for example langmap.kak and therefore rely on powerline.kak. So if we're going to load plugins we should load powerline before langmap. We can do it like so:
But if there are many plugins in
kakrc
it gets harder every time to figure out the order and move plugins around is a tedious task. So instead of keeping an order, it could be set withafter
keyword:This way the order load will be as follows:
Not sure how useful this feature will be, but there are some other plugins already that depend on other plugins, for example: kakoune-emmet depends on kakoune-snippets
The text was updated successfully, but these errors were encountered: