yazi
yazi copied to clipboard
File info not auto update
What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
Windows Terminal
Yazi version
0.2.3
Did you try the latest main branch to see if the problem got fixed?
Tried, but the problem still
Describe the bug
不通过yazi的manager命令来修改文件,修改后,文件信息没有更新
Expected Behavior
auto update file info
To Reproduce
比如:在外部使用 chmod
修改文件权限后,yazi显示的不是最新的权限
Configuration
No response
Anything else?
No response
I can't reproduce this issue in the latest main branch.
I noticed you mentioned trying the latest main branch - which commit are you trying? Please do a yazi -V
and paste the version here.
https://github.com/sxyazi/yazi/assets/17523360/b9191a46-ddc0-4f4e-8b88-91a098d81281
Translated to English using Google Translate:
Sorry, the complete version information is not pasted.
I have currently updated from 0.2.3
to 0.2.4
, but the issue remains.
yazi -V
result: yazi 0.2.4 (Arch Linux 2024-03-10)
Tmux: 3.4
System: ArchLinux (Latest)
Here is the video running based on this version in Tmux:
抱歉,没有贴全部的版本信息
我目前从 0.2.3
更新到 0.2.4
问题依旧
yazi -V
结果:yazi 0.2.4 (Arch Linux 2024-03-10)
Tmux:3.4
系统:ArchLinux(Latest)
以下是我基于这个版本在Tmux中运行的视频:
https://github.com/sxyazi/yazi/assets/45219522/eb09c1fa-3e7f-45f1-a9b1-107d09dc2489
Please do a yazi --debug
and paste the output here.
yazi --debug
:
Yazi
yazi 0.2.4 (Arch Linux 2024-03-10)
Environment
OS: linux-x86_64 (unix)
Debug: false
Emulator
Emulator.via_env: ("xterm-256color", "")
Emulator.via_csi: Ok(Unknown([]))
Emulator.detect: Unknown([])
Adaptor
Adaptor.matches: KittyOld
tmux
TMUX: false
Zellij
ZELLIJ_SESSION_NAME: None
Desktop
XDG_SESSION_TYPE: None
WAYLAND_DISPLAY: None
DISPLAY: None
Ueberzug
Version: Err(Os { code: 2, kind: NotFound, message: "No such file or directory" })
WSL
/proc/sys/fs/binfmt_misc/WSLInterop: true
--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/home/sky03/.local/state/yazi" directory.
and the log file:
2024-03-11T11:59:39.728384Z WARN yazi_adaptor::emulator: [Adaptor] No special environment variables detected
at yazi-adaptor/src/emulator.rs:64
2024-03-11T11:59:39.728427Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM_PROGRAM:
at yazi-adaptor/src/emulator.rs:77
2024-03-11T11:59:39.728430Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM: xterm-256color
at yazi-adaptor/src/emulator.rs:84
2024-03-11T11:59:39.729416Z WARN yazi_adaptor::adaptor: [Adaptor] Could not identify XDG_SESSION_TYPE
at yazi-adaptor/src/adaptor.rs:107
2024-03-11T11:59:39.730431Z WARN yazi_adaptor::emulator: [Adaptor] No special environment variables detected
at yazi-adaptor/src/emulator.rs:64
2024-03-11T11:59:39.730469Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM_PROGRAM:
at yazi-adaptor/src/emulator.rs:77
2024-03-11T11:59:39.730472Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM: xterm-256color
at yazi-adaptor/src/emulator.rs:84
2024-03-11T11:59:39.730922Z WARN yazi_adaptor::emulator: [Adaptor] No special environment variables detected
at yazi-adaptor/src/emulator.rs:64
2024-03-11T11:59:39.730959Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM_PROGRAM:
at yazi-adaptor/src/emulator.rs:77
2024-03-11T11:59:39.730961Z WARN yazi_adaptor::emulator: [Adaptor] Unknown TERM: xterm-256color
at yazi-adaptor/src/emulator.rs:84
2024-03-11T11:59:39.731366Z WARN yazi_adaptor::adaptor: [Adaptor] Could not identify XDG_SESSION_TYPE
at yazi-adaptor/src/adaptor.rs:107
You are in WSL right? What's your file system?
Yes, I use ArchLinux in WSL, and the file system I use is ext4
.
(WSL2 only support the ext4
file system.)
There's a similar report https://github.com/sxyazi/yazi/issues/1017 to your issue, and it was fixed in https://github.com/sxyazi/yazi/pull/1024.
Please try this fix if it works for you. (need to build from the latest main branch atm).
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
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.