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
Please describe the problem you're trying to solve
I generate part of my config with nix https://nixos.org/. It has several advantages, one of which is for general toggle of a plugin.
For instance I have a nix setting yazi.enableOuchPlugin = true that enables the yazi plugin https://github.com/ndtoan96/ouch.yazi:
it puts the plugin files where expected (in ~/.config/yazi/plugins/ouch.yazi), makes "ouch" available to the plugin and enables the config advised in the plugin, i.e. the previewers and loaders.
The drawback is that generating ~/.config/yazi/yazi.toml via nix, the file becomes read-only and any change to the config becomes bothersome because it takes several seconds for nix to regenerate the config.
Would you be willing to contribute this feature?
Yes, I'll give it a shot
Describe the solution you'd like
What I try to when possible do is to get the best of both worlds by merging:
a configuration generated by nix
an imperative configuration I can quickly edit/save/restart the software
Now I dont know how to do this with yazi, I dont think it's possible ?
Outside of my specific nix usecase, maybe this feature could be used by plugins to embed their own configuration ?
The possible ways to do it I could think of:
add an "include" directive in yazi.toml
have a "config.d" folder like for ssh, where all files in this folder are loaded
have plugins embed their own yazi.toml that can be merged
have a lua API to load the different configuration files (keymap/yazi.toml etc)
I think introducing config merging for a performance-first file manager is a bit overkill (it will require reading more files and doing more merges), and it could also cause more confusion - I've explained my thoughts in more detail in another issue here, #989 (comment)
Please describe the problem you're trying to solve
I generate part of my config with nix https://nixos.org/. It has several advantages, one of which is for general toggle of a plugin.
For instance I have a nix setting
yazi.enableOuchPlugin = true
that enables the yazi plugin https://github.com/ndtoan96/ouch.yazi:it puts the plugin files where expected (in ~/.config/yazi/plugins/ouch.yazi), makes "ouch" available to the plugin and enables the config advised in the plugin, i.e. the previewers and loaders.
The drawback is that generating ~/.config/yazi/yazi.toml via nix, the file becomes read-only and any change to the config becomes bothersome because it takes several seconds for nix to regenerate the config.
Would you be willing to contribute this feature?
Describe the solution you'd like
What I try to when possible do is to get the best of both worlds by merging:
Now I dont know how to do this with yazi, I dont think it's possible ?
Outside of my specific nix usecase, maybe this feature could be used by plugins to embed their own configuration ?
The possible ways to do it I could think of:
Additional context
#623 might be related
The text was updated successfully, but these errors were encountered: