Switching from a non-rerversed sorting to a reversed sorting, back to a non-reversed sorting, keeps the reversion.

[ThGrSoRu]

What system are you running Yazi on?

Linux Wayland

What terminal are you running Yazi in?

foot version: 1.17.2 +pgo +ime +graphemes -assertions

Did you try the latest code to see if this problem got fixed?

Tried, but the problem still

yazi --debug output

```sh Yazi Version: 0.2.5 (Arch Linux 2024-06-08) Debug : false OS : linux-x86_64 (unix) Ya Version: 0.2.5 Emulator Emulator.via_env: ("foot-extra", "") Emulator.via_csi: Ok(Foot) Emulator.detect : Foot Adaptor Adaptor.matches: Sixel Desktop XDG_SESSION_TYPE: Some("wayland") WAYLAND_DISPLAY : Some("wayland-1") DISPLAY : Some(":0") SSH shared.in_ssh_connection: false WSL /proc/sys/fs/binfmt_misc/WSLInterop: false Variables SHELL : Some("/bin/fish") EDITOR : Some("micro") ZELLIJ_SESSION_NAME: None YAZI_FILE_ONE : None YAZI_CONFIG_HOME : None Text Opener default: Some(Opener { run: "$EDITOR \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true }) block : Some(Opener { run: "$EDITOR \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true }) tmux TMUX : false Version: No such file or directory (os error 2) Dependencies file : 5.45 ueberzugpp : No such file or directory (os error 2) ffmpegthumbnailer: 2.2.2 magick : 7.1.1-33 fzf : 0.53.0 fd : 10.1.0 rg : 14.1.0 chafa : 1.14.0 zoxide : 0.9.4 unar : 1.10.7 jq : 1.7.1 ```

Describe the bug

Starting with sort --dir-first natural, then sort modified --reverse --dir-first, then going back to sort --dir-first natural, does sort natural --reverse --dir-first instead.

This does not to happen when switching from sort --dir-first natural to sort size --dir-first back to sort --dir-first natural.

Expected Behavior

Sorting should not be reversed when choosing a non-reversed sorting.

To Reproduce

See above.

Configuration

No response

Anything else?

No response

[sxyazi]

See https://github.com/sxyazi/yazi/issues/1046

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days. ⏳ This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.