Q: Run a shell command default arguments

[VKondakoff]

Hi!

I'm just experimenting with Run a shell command, invoked by pressing ; or : hotkey. Here is what I noticed: everything is OK if I'm writing something like this in the input field (open hovered file with default app):
open $0
But is I omit the argument and input just open command stops to work and here is what I see in Task manager:

So, there are two instances of currently hovered file in command line. Why this happens? Bug? Or am I doing something wrong?

[sxyazi]

These two paths are identified as $0 and $1, which means you can use $0 and $1 in the shell. Of course, you don't have to use them, but Yazi always passes them to ensure they are available when needed.

[VKondakoff]

Got it, thank you. But I think it would be more user friendly to set the default arguments for Run a shell command like this:

1. If there is nothing selected add $0 to the user specified command
2. If there are some files/folders selected add $@ to the user specified command

[sxyazi]

When no file is selected (only hovering over a file), $0 == $1. This provides convenience for the user: for openers that support opening multiple files, $@ will always be available. Conversely, if only $0 is available, $@ will no longer be available since $0 is not considered part of $@, requiring users to write two sets of commands for programs that support both multiple and single paths. On the other hand, $0 is an extension by Yazi and doesn't belong to any standard, while $1 is always available, aligning with shell behavior.