[manish0467]

Summary

Adds an integration plugin for the Yazi terminal file manager under installer/linux/yazi/filee.yazi/.

Similar to the existing GNOME Shell extension, KWin script, and Hyprland rules in installer/linux/, this plugin enables Linux / terminal users to interact with Filee directly from within Yazi.

Features

• Multi-target selection: Works on multi-file selections or falls back to the currently hovered file.
• Interactive Quick-Convert Menu (ya.which):
  • Images: WebP, JPEG, PNG, AVIF, Remove Background
  • Documents: PDF, OCR to Markdown (.md), OCR to Plain Text (.txt)
  • Media: Extract Audio (MP3), Compress Video (MP4)
  • Archives: ZIP, Extract
  • Custom format prompt via ya.input
  • GUI: Open files directly in the interactive Filee Donut
• Non-blocking asynchronous conversion: Runs conversions in the background without locking the terminal file manager.
• Notifications: Uses Yazi's built-in ya.notify() for in-terminal progress/completion, and sends desktop notifications via standard freedesktop notify-send if installed.

Packaging & Documentation

• Bundled into the Linux release package in build/build-portable.ps1.
• Setup instructions and keybinding example documented in installer/linux/INSTALL.txt and installer/linux/yazi/filee.yazi/README.md.

[KnifeLemon]

Thanks, @manish0467! A Yazi plugin fits well next to the KWin, GNOME and Hyprland pieces, and the CLI calls are right: filee convert … --to / --preset, and the remove-background and extract presets exist. The install path in INSTALL.txt matches where install.sh puts the app.

A few things before it can go in:

1. Drop --- @sync entry (first line of init.lua). With it, entry runs in Yazi's sync context. But ya.which, ya.input and the ya.sync wrapper (get_targets) only work in the async context, so the menu can't open there. And cmd:output() in a sync entry would freeze Yazi until the conversion ends, which is the opposite of the "non-blocking" in the description. Without the annotation the entry runs async, get_targets through ya.sync is the right way to read the selection, and output() waits without blocking the UI.
2. The keymap section. Yazi renamed manager to mgr in its config (25.5). Please use [[mgr.prepend_keymap]] in both INSTALL.txt and the plugin's README, and say which Yazi version the plugin needs.
3. "Open in Filee Donut" fallbacks. ~/.local/bin/filee is the CLI (filee-cli), which has no --convert option, and install.sh doesn't put a Filee on PATH. The installed app path you try first is the right one. Please drop the two fallbacks, and show a ya.notify error when the app can't be started, instead of always reporting "Opened".
4. Could you say which Yazi version you tested it with, and how (selection, hovered file, the custom-format prompt)? A short note in the PR is enough.

Thanks again!

[manish0467]

Hi @KnifeLemon, thank you very much for the review and helpful pointers!

I have addressed all the feedback in the latest commit:

1. Dropped --- @sync entry: Removed the annotation so M:entry() executes in Yazi's async context. The get_targets call via ya.sync still safely reads the selection/hover state from the UI thread, and CLI execution cmd:output() awaits asynchronously without freezing the UI.
2. Keymap section & version requirements: Updated the keymap config in both INSTALL.txt and installer/linux/yazi/filee.yazi/README.md to use the modern [[mgr.prepend_keymap]] syntax, and noted the requirement for Yazi 25.5+ (along with the legacy fallback for older versions).
3. Donut launcher cleanup & error notification: Dropped the CLI fallback commands and added an explicit ya.notify(..., "error") notification if launching the GUI fails or the binary is missing, rather than reporting success unconditionally.
4. Testing details:
   • Tested on Yazi 26.9.1 (x86_64-unknown-linux-gnu).
   • Verified with:
     • Single hovered file conversion.
     • Multi-file visual selection (<Space> multi-select).
     • Custom format prompt via ya.input (e.g. svg, docx).
     • "Open in Filee Donut" launch with files passed to --convert.
     • In-terminal notifications via ya.notify() and system notifications via notify-send.

All unit tests (dotnet test tests/Filee.Platform.Tests) pass cleanly as well. Thanks again!