About yazi.toml

[poontology]

Couple issues/ideas,

1. on linux xdg-open by default doesn't know how to run .AppImage, not yazi's fault of course but IMO it'd be nice if yazi defaulted to having an opener that executed *.AppImage as-is (if it has +x bit).
2. It took me better part of an hour to figure out how to get yazi to run AppImage because while there's a GH issue and a GH discussion about this very topic the simple solution given on those pages doesn't work because the config format changed some months ago (after PR feat!: virtual file system #3034 opener "name" is "url" now) but because the issue and discussion are locked I can't leave a comment to help future people who no doubt arrive there trying to solve the same issue because those are the top-most google hits for "yazi appimage", do they need to be locked?
3. yazi doesn't say anything about the wrong config, it just fails to work. it'd be nice if it alerted the user about deprecated config file syntax and point them to a changelog that covers the various syntax changes from one version to the next. (wish hyprland had this, been having to dig into commit history several times a year to figure out how they broke my configs this time.)

[WXLF17]

● If you're hitting this in Yazi 26.x, the community answers above are outdated.

The [open] rules field was renamed from name to url (I think around v0.3+).
Using name = is silently ignored — Yazi falls back to the default xdg-open
rule, which on most Linux systems fails with no method available for opening
since AppImages don't register a MIME handler.

Working config for Yazi 26.x:

  [opener]
  appimage = [
    { run = '%s', desc = "Run AppImage", orphan = true, for = "unix" },
  ]

  [open]
  prepend_rules = [
    { url = "*.AppImage", use = [ "appimage" ] },
    { url = "*.appimage", use = [ "appimage" ] },
  ]

  Key points:
  - url (not name) for [open] rules
  - %s for argument substitution (not $0/$1/$@)
  - orphan = true to detach the GUI process from Yazi
  - Make sure the AppImage is executable: chmod +x file.AppImage

  Fully restart Yazi after editing (pkill yazi) — it reads config only at startup.