yazi: zoxide plugin not working

What system are you running Yazi on?

Linux Wayland

What terminal are you running Yazi in?

wezterm 20240203-110809-5046fc22

yazi --debug output

Yazi
    Version: 25.2.11 (ce9092e 2025-02-11)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.84.1 (e71f9a9a 2025-01-27)

Ya
    Version: 25.2.11 (ce9092e 2025-02-11)

Emulator
    TERM                : Some("xterm-256color")
    TERM_PROGRAM        : Some("WezTerm")
    TERM_PROGRAM_VERSION: Some("20240203-110809-5046fc22")
    Brand.from_env      : Some(WezTerm)
    Emulator.detect     : Emulator { kind: Left(WezTerm), light: false, cell_size: Some((10, 22)) }

Adapter
    Adapter.matches: Sixel

Desktop
    XDG_SESSION_TYPE           : Some("wayland")
    WAYLAND_DISPLAY            : Some("wayland-1")
    DISPLAY                    : Some(":1")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Neovim
    NVIM          : false
    Neovim version: No such file or directory (os error 2)

Variables
    SHELL           : Some("/home/lucca/.cargo/bin/nu")
    EDITOR          : Some("/home/lucca/user_installs/helix/target/release/hx")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: None

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

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

Dependencies
    file          : 5.45
    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        : No such file or directory (os error 2)
    fzf           : 0.44.1
    fd/fdfind     : No such file or directory (os error 2) / 9.0.0
    rg            : No such file or directory (os error 2)
    chafa         : No such file or directory (os error 2)
    zoxide        : 0.9.7
    7zz/7z        : No such file or directory (os error 2) / 23.01
    jq            : 1.7

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

Describe the bug

when i press z to activate the zoxide plugin, yazi just turns to black (the color of my background)

Minimal reproducer

when i press z to activate the zoxide plugin, yazi just turns to black (the color of my background)

Anything else?

before pressing z

Image

after:

Image

Checklist

  • I tried the latest nightly build, and the issue is still reproducible
  • I updated the debug information (yazi --debug) input box to the nightly that I tried
  • I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 37 (12 by maintainers)

Most upvoted comments

Thanks for confirming @Avi0 @luccahuguet!

It really looks like this is an fzf bug then, especially since the zoxide integration code in Yazi hasn’t been changed at all recently.

I’ll mark the issue as “invalid” now since it’s not a problem with Yazi itself. Thanks again to everyone for helping investigate this!

Some more info: screen goes blank after pressing z, but you can actually type something and press enter, and yazi will switch to a directory matched to what you typed. zoxide works, but the screen is blank during directory selection.

I was having this issue, it started sometime after v0.4.2

I tried v25.3.7 and had he issue, but also had tried an earlier newer version some time ago and had that issue.

Just upgraded fzf 0.48.1 -> 0.60.3 and now the issue is gone and it is working

can we reopen this issue? feels like something under the yazi umbrella

also, thanks for the info @Avi0 this is super useful

Sure, here you go @luccahuguet


Yazi
    Version: 25.2.11 (7b4c4ea 2025-02-23)
    Debug  : false
    Triple : aarch64-apple-darwin (macos-aarch64)
    Rustc  : 1.85.0 (4d91de4e 2025-02-17)

Ya
    Version: 25.2.11 (7b4c4ea 2025-02-23)

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

Adapter
    Adapter.matches: Kgp

Desktop
    XDG_SESSION_TYPE           : None
    WAYLAND_DISPLAY            : None
    DISPLAY                    : None
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL           : Some("/opt/homebrew/bin/zsh")
    EDITOR          : Some("nvim")
    VISUAL          : Some("nvim")
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: Some("\n--reverse --ansi --no-multi\n--bind=ctrl-u:up,ctrl-e:down,ctrl-n:backward-char,ctrl-i:forward-char,ctrl-b:backward-word,ctrl-h:forward-word\n--border --color=dark\n--color=fg:-1,bg:-1,hl:#5fff87,fg+:-1,bg+:-1,hl+:#ffaf5f\n--color=info:#af87ff,prompt:#5fff87,pointer:#ff87d7,marker:#ff87d7,spinner:#ff87d7\n")

Text Opener
    default     : Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-create: Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block-rename: Some(Opener { run: "${EDITOR:=vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : tmux 3.5a
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : 0.41.2

Dependencies
    file          : 5.41
    ueberzugpp    : No such file or directory (os error 2)
    ffmpeg/ffprobe: 7.1 / 7.1
    pdftoppm      : 25.02.0
    magick        : 7.1.1-44
    fzf           : 0.60.1
    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: No such file or directory (os error 2) / No such file or directory (os error 2)
    xclip        : No such file or directory (os error 2)
    xsel         : No such file or directory (os error 2)


See https://yazi-rs.github.io/docs/plugins/overview#debugging on how to enable loggingor debug runtime errors.

That’s weird, I still can’t reproduce it. It’s likely an environment-specific issue. Try debugging it further to see if there’s a way to fix it.

On Sat, Feb 22, 2025 at 7:40 PM Kikis @.***> wrote:

I don’t think so, downgrading yazi to 0.4.2-1 was the only way I could get it to work again. The plugin wouldn’t work regardless of zoxide version and if I rebuilt it from scratch. Maybe something is wrong from my end in terms of configuration but I can’t pinpoint it.

— Reply to this email directly, view it on GitHub https://github.com/sxyazi/yazi/issues/2360#issuecomment-2676160141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFWFIBM7U6RSO5MACTBBQT2RBO33AVCNFSM6AAAAABXMEK3G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGE3DAMJUGE . You are receiving this because you modified the open/close state.Message ID: @.***> [image: kikisprdx]kikisprdx left a comment (sxyazi/yazi#2360) https://github.com/sxyazi/yazi/issues/2360#issuecomment-2676160141

I don’t think so, downgrading yazi to 0.4.2-1 was the only way I could get it to work again. The plugin wouldn’t work regardless of zoxide version and if I rebuilt it from scratch. Maybe something is wrong from my end in terms of configuration but I can’t pinpoint it.

— Reply to this email directly, view it on GitHub https://github.com/sxyazi/yazi/issues/2360#issuecomment-2676160141, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFWFIBM7U6RSO5MACTBBQT2RBO33AVCNFSM6AAAAABXMEK3G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGE3DAMJUGE . You are receiving this because you modified the open/close state.Message ID: @.***>

I don’t think so, downgrading yazi to 0.4.2-1 was the only way I could get it to work again. The plugin wouldn’t work regardless of zoxide version and if I rebuilt it from scratch. Maybe something is wrong from my end in terms of configuration but I can’t pinpoint it.

Try debugging it and see what’s wrong.

Closing for now since I still can’t reproduce it. Please reopen if you find a sure way of reproducing the issue.