Closed dangooddd closed 5 days ago
Duplicate of https://github.com/sxyazi/yazi/issues/1408
I want to keep it simple – it's just about automating the step of manually downloading plugins from GitHub.
Since it supports monorepos, supporting that would require introducing a third directory, which makes the design and implementation more complex. It also breaks the convention of the plugin directory location, because plugins would come from two directories, which introduces the need for a separate priority concept – which plugin should be used when two directories have a plugin with the same name?
This increases confusion while reducing transparency for users – it's easy for me to know where Yazi's config directory is, but it's hard to say where the data directory storing plugins is, which makes it harder for users to find their plugins.
Also, since plugins could come from two directories, every time we load plugins, an extra check is needed, which affects performance. Plus, it would break other features in Yazi, like the YAZI_CONFIG_PATH
environment variable. These issues are also present in flavor.
I've provided a more detailed explanation in the linked issue, please read it. Closing as duplicate and not planned.
yazi --debug
outputPlease describe the problem you're trying to solve
Currently flavors and plugins stored at config directory. In my opinion these type of data should be stored at data folder (~/.local/share/yazi or $XDG_CONFIG_HOME/yazi). Is there any good reason to store that in config folder? For example nvim stores plugins in data folder.
Also some people don't want to store source code of plugins and flavors with licenses in their dotfiles repos. It will be more consistent to not add anything like that in .gitignore file
Would you be willing to contribute this feature?
Describe the solution you'd like
Add option to ya pack to install plugins and flavors in data folder instead of config folder or make it default behavior
Additional context
No response
Validations