Use `command` (POSIX) and `^` (Nushell) to prevent recursive function calls when `cfg.shellWrapperName` is set to "yazi". Previously, if `cfg.shellWrapperName` was set to "yazi", the invocation of `yazi` within the shell integration function triggered the function itself instead of the binary. This name conflict prevents users from using the binary name as-is when shell integration is enabled. Hence, fix this by using shell-specific mechanisms to target the underlying executable, bypassing any name collisions. This aligns with the official documentation: - |
||
|---|---|---|
| .. | ||
| empty | ||
| flavor | ||
| plugin | ||
| bash-integration-enabled.nix | ||
| default.nix | ||
| fish-integration-enabled.nix | ||
| fish-integration-expected.fish | ||
| init-lua-string.nix | ||
| init.lua | ||
| keymap-expected.toml | ||
| nushell-integration-enabled.nix | ||
| settings-expected.toml | ||
| settings.nix | ||
| theme-expected.toml | ||
| zsh-integration-enabled.nix | ||