Re: New package: yazi-0.2.5

[sxyazi <sxyazi@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

New comment by sxyazi on void-packages repository

https://github.com/void-linux/void-packages/pull/46909#issuecomment-2083134057

Comment:
Yazi will **NOT** randomly delete user files. 

On the contrary, we've made extensive security efforts. For example:

- The default behavior for deletion ([`remove` command](https://yazi-rs.github.io/docs/configuration/keymap/#manager.remove)) is to move files to the trash instead of permanently deleting them. If users want to permanently delete files, they need to manually specify `--permanently`, and there's a confirmation prompt for every deletion even trashing.
- For shell commands like [`shell "nvim"`](https://yazi-rs.github.io/docs/configuration/keymap/#manager.shell), by default, a dialog box pops up displaying the shell command template passed by the user for confirmation, and the command isn't executed. It's only executed if the user explicitly specifies `shell "nvim" --confirm`. 
- Splitting the commands/keys for [opening](https://yazi-rs.github.io/docs/configuration/keymap/#manager.open) and [entering directories](https://yazi-rs.github.io/docs/configuration/keymap/#manager.enter) also includes security considerations. Users navigate between files using Vim-like `hjkl` keys, and when they're sure they want to open/run the selected file, they use `<Enter>` instead of using `l` like in other file managers, which is used for both directory navigation and opening files. 
- We've implemented a [nested selection conflict detection](https://github.com/sxyazi/yazi/issues/688) to prevent users from selecting `/a/b` while also selecting `/a`, as their mutual inclusion could lead to file confusion.
- In the previous version, we also added [detection for the same directory](https://github.com/sxyazi/yazi/issues/894) to prevent users from copying `./foo` as `./foo/foo`, `./foo/foo/foo`, which would result in recursive copying. 

Having said all that, I just want to emphasize that **security is always Yazi's top priority**, and this shouldn't be a reason to prevent this PR from being merged (if it is).