You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A couple of days ago, I started to notice, that sorting by mtime stopped working for me.
I didn't change my config before it stopped working.
If it is relevant: The behavior doesn't change depending on whether the files are on ext4 or btrfs.
I confirmed this issue on two Arch Linux installs; however, it does work in a Kali VM.
I tested with the latest Arch package from the extra repository (0.4.2) and the latest nightly release (see my yazi --debug).
The issue does go away if the config is "deleted" (renamed), as mentioned before, however, I don't think I can relate a config change I dit to the issue.
Minimal reproducer
As far as I am aware, all that is needed is:
Install yazi
do something to the configuration
Try to sort files by mtime
Anything else?
Here is a short video demonstrating the behavior:
test.mp4
Here is my config (renamed to .txt because of attachment restrictions):
{ on = [ ",", "m" ], run = [ "sort modified --reverse=no", "linemode mtime" ], desc = "Sort by modified time" },
{ on = [ ",", "M" ], run = [ "sort modified --reverse", "linemode mtime" ], desc = "Sort by modified time (reverse)" },
in your keymap.toml. sort modified has been renamed to sort mtime in Yazi 0.4, so you need to change it in your config file, see #1772 for more details
What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
kitty 0.38.1
yazi --debug
outputDescribe the bug
A couple of days ago, I started to notice, that sorting by mtime stopped working for me.
I didn't change my config before it stopped working.
If it is relevant: The behavior doesn't change depending on whether the files are on ext4 or btrfs.
I confirmed this issue on two Arch Linux installs; however, it does work in a Kali VM.
I tested with the latest Arch package from the extra repository (0.4.2) and the latest nightly release (see my
yazi --debug
).The issue does go away if the config is "deleted" (renamed), as mentioned before, however, I don't think I can relate a config change I dit to the issue.
Minimal reproducer
As far as I am aware, all that is needed is:
Anything else?
Here is a short video demonstrating the behavior:
test.mp4
Here is my config (renamed to .txt because of attachment restrictions):
yazi.txt
keymap.txt
smart-enter-init.txt
Checklist
yazi --debug
) input box to the nightly that I triedmv ~/.config/yazi ~/.config/yazi-backup
)The text was updated successfully, but these errors were encountered: