add path towards log file in --debug

[teto]

yazi --debug output

Yazi
    Version: 25.2.11 (1ddbbfe 2025-02-17)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.84.0 (9fc6b431 2025-01-07)

Ya
    Version: 25.2.11 (1ddbbfe 2025-02-17)

Emulator
    TERM                : Some("xterm-kitty")
    TERM_PROGRAM        : None
    TERM_PROGRAM_VERSION: None
    Brand.from_env      : Some(Kitty)
    Emulator.detect     : Emulator { kind: Left(Kitty), light: true, cell_size: Some((10, 21)) }

Adapter
    Adapter.matches: Kgp

Desktop
    XDG_SESSION_TYPE           : Some("wayland")
    WAYLAND_DISPLAY            : Some("wayland-1")
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : Some("/run/user/1000/sway-ipc.1000.3654460.sock")
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL           : Some("/nix/store/p6k7xp1lsfmbdd731mlglrdj2d66mr82-bash-5.2p37/bin/bash")
    EDITOR          : Some("nvim")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: Some("--bind=\'ctrl-o:execute(code {})+abort\' --bind=\'ctrl-o:execute(code {})+abort\'")

Text Opener
    default     : Some(Opener { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for_: None, spread: false })
    block-create: Some(Opener { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for_: None, spread: false })
    block-rename: Some(Opener { run: "xdg-open \"$1\"", block: true, orphan: false, desc: "xdg-open", for_: None, spread: false })

Multiplexers
    TMUX               : false
    tmux version       : No such file or directory (os error 2)
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file          : 5.46
    ueberzugpp    : No such file or directory (os error 2)
    ffmpeg/ffprobe: No such file or directory (os error 2) / No such file or directory (os error 2)
    pdftoppm      : 24.02.0
    magick        : 7.1.1-43
    fzf           : 0.60.0
    fd/fdfind     : 10.2.0 / No such file or directory (os error 2)
    rg            : 14.1.1
    chafa         : 1.14.5
    zoxide        : 0.9.7
    7zz/7z        : 24.09 / No such file or directory (os error 2)
    jq            : 1.7.1

Clipboard
    wl-copy/paste: 2.2.1 / 2.2.1
    xclip        : 0.13
    xsel         : No such file or directory (os error 2)

Please describe the problem you're trying to solve

yazi was throwing advice on how to update my yazi plugin (which is pretty awesome) but I wanted more details / was unsure why my plugin stopped working. I had forgotten where to look for the logfile (it's explained here https://yazi-rs.github.io/docs/plugins/overview/#logging)

Would you be willing to contribute this feature?

• Yes, I'll give it a shot

Describe the solution you'd like

would be nice to add path towards logfile to yazi --debug in case someone has no internet access (would be worth mentioning in manpage as well IMO https://github.com/yazi-rs/manpages/blob/main/yazi.1).

Additional context

No response

Checklist

• I have searched the existing issues/discussions
• The latest nightly build doesn't already have this feature

[sxyazi]

I don't want to include another logging or debugging guide in yazi --debug since that would mean maintaining two separate copies of the documentation. However, I'm fine with adding a link to the command output.

As for the manpage, since it's designed for offline access, I don't mind including another copy of the guide if it helps offline users.

[sxyazi]

adding a link to the command output

Done in #2365

including another copy of the guide if it helps offline users

Noted in yazi-rs/manpages#3

[github-actions]

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 file a new issue and complete the issue template so we can capture all the details necessary to investigate further.