Store plugins and flavors in data folder (~/.local/share/yazi or $XDG_DATA_HOME/yazi)

[dangooddd]

I wonder is there a reason to store flavors and plugins in config directory? In my opinion, it is better to store it in data directory.

I think many people including me put those directories in gitignore because dont want to store plugin/flavor source code in their dotfiles repo.

Also, nvim for example stores plugins in data folder, so why we choose this approach?

[xfzv]

Agreed, this would be much cleaner.

As far as I'm concerned, I'm using chezmoi to manage my dotfiles. chezmoi allows to include dotfiles from elsewhere so I can have for example ~/dotfiles/.chezmoiexternals/yazi.toml:

[".config/yazi/plugins/augment-command.yazi/init.lua"]
type = "file"
url = "https://raw.githubusercontent.com/hankertrix/augment-command.yazi/main/init.lua"
refreshPeriod = "168h"

[".config/yazi/plugins/chmod.yazi/init.lua"]
type = "file"
url = "https://raw.githubusercontent.com/yazi-rs/plugins/main/chmod.yazi/init.lua"
refreshPeriod = "168h"

With this approach:

• I don't have to add yazi plugins directory to .gitignore or .chezmoiignore
• The file is updated every 168 hours (customizable) when I run chezmoi update or chezmoi apply so I don't have to have the Git repo cloned locally and to run git pull.

[sxyazi]

Duplicate of #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.