Replies: 3 comments 7 replies
-
There's no config like that yet. You can always have different config files and load them when starting zellij like this: but it's not that they loaded config will be merged with the default |
Beta Was this translation helpful? Give feedback.
-
Are the Zellij maintainers opposed to supporting some form of "include" for config files? My use case is sharing Zellij across several machines. I want the structure of my layout but the actual commands need to change for work or personal or whatever. I would love to have one config, a common layout template file which defines a tab and pane template, and then the actual layout being used which imports / includes those templates and does what I need for the particular scenario. |
Beta Was this translation helpful? Give feedback.
-
What if we side step that, at least initially. What if we put a template in one file say default.templatr.kdl and then if that exists those templates are used when the layout is loaded. Separately, I don't see why kdl needs to support this. XML and similar formats allowed the user/developer to define their own functionality. If an "include" is encountered it is up to the app parsing it to handle it. |
Beta Was this translation helpful? Give feedback.
-
Hi I am really new to zellij but it sounds great and looks really interesting.
I myself am a fan of how nvim uses lua for it's configs because the scripting aside you can spread the config into multiple files and then just require the files.
Some people might not like that approach but I think it makes your config really clean and tidy.
So I was wondering, if there is also a way for zellij to have it's configuration spread out over multiple files?
Since zellij is using kdl for configuration(which can't include files by how I understood it) is there maybe an option in zellij to use multiple config files just like one could do the same thing with layouts and themes by setting theme_dir and layouts_dir?
Beta Was this translation helpful? Give feedback.
All reactions