gvim :!yazi Linux incorrect response

[Konfekt]

What system are you running Yazi on?

Linux X11

What terminal are you running Yazi in?

gvim 9.2.140

yazi --debug output

zsh $ yazi --debug

Yazi
    Version: 26.1.22 (4e0acf8 2026-01-22)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.93.0 (254b5960 2026-01-19)

Ya
    Version: 26.1.22 (4e0acf8 2026-01-22)

Config
    Init             : /home/konfekt/.config/yazi/init.lua (No such file or directory (os error 2))
    Yazi             : /home/konfekt/.config/yazi/yazi.toml (No such file or directory (os error 2))
    Keymap           : /home/konfekt/.config/yazi/keymap.toml (No such file or directory (os error 2))
    Theme            : /home/konfekt/.config/yazi/theme.toml (No such file or directory (os error 2))
    VFS              : /home/konfekt/.config/yazi/vfs.toml (No such file or directory (os error 2))
    Package          : /home/konfekt/.config/yazi/package.toml (No such file or directory (os error 2))
    Dark/light flavor: "" / ""

Emulator
    TERM                : Some("xterm-ghostty")
    TERM_PROGRAM        : Some("ghostty")
    TERM_PROGRAM_VERSION: Some("1.3.0")
    Brand.from_env      : Some(Ghostty)
    Emulator.detect     : Emulator { kind: Left(Ghostty), version: "ghostty 1.3.0", light: true, csi_16t: (13, 23), force_16t: false }

Adapter
    Adapter.matches    : Kgp
    Dimension.available: Dimension { rows: 28, columns: 84, width: 1092, height: 644 }

Desktop
    XDG_SESSION_TYPE           : Some("x11")
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL              : Some("/bin/zsh")
    EDITOR             : Some("vim")
    VISUAL             : Some("vim")
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None
    YAZI_ZOXIDE_OPTS   : None

Text Opener
    default     : Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true })
    block-create: Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true })
    block-rename: Some(OpenerRule { run: "${EDITOR:-vi} %s", block: true, orphan: false, desc: "$EDITOR", for: None, spread: true })

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

Dependencies
    file          : 5.41
    ueberzugpp    : 2.9.7
    ffmpeg/ffprobe: 4.4.2-0 / 4.4.2-0
    pdftoppm      : 22.02.0
    magick        : No such file or directory (os error 2)
    fzf           : 0.70.0
    fd/fdfind     : 8.3.1 / 8.3.1
    rg            : 13.0.0
    chafa         : 1.8.0
    zoxide        : 0.4.3
    7zz/7z        : 21.07 / 16.02
    resvg         : No such file or directory (os error 2)
    jq            : 1.6

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

Routine
    `file -bL --mime-type`: text/plain


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

Describe the bug

Running :!yazi with empty config inside gvim --clean -u NONE (empty config) with Yazi 26.1.22 (4e0acf8 2026-01-22) in Ubuntu 22.04 yields

7_Gi=31,s=1,v=1,a=q, t=d, f=24;AAAA\ [>q[16t]11;?[0c1[38;5;9m[1m

Terminal response timeout: [Om[OmThe request sent by Yazi didn't receive a correct response

Please check your terminal environment as per: https: //yazi-rs.github.io/docs/faq#trt

[?1049hP$q q\[?12$p[?u[0c[?2004h[?1004h[?1000h[?1002h[?1003h[?1015h[?1006?[38;5;9m[1m

Terminal response timeout: [Om[OmThe request sent by Yazi didn't receive a correct response

Please check your terminal environment as per: https: //yazi-rs.github.io/docs/faq#trt

]0:yazi - -/[?251[2J[39m[49m[59m[Om]0;yazi - -/debug[?2026h[39m[49m[59m[Om[?251[?20261]0;yazi - -/[?2026h[39m[49m[59m[Om[?251[?2026m[?2026h[39m[49m[59m[oOm[?251
?20261[?2026h[39m[49m[59m[Om[?251[?2026?[?2026h[39m[49m[59m[Om[?2511?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59mLOm[?2511?2026m[?2026h[39m[49m
S9m[Om[?2511?20261[?2026h[39m[49m[59m[Om[?251[?20262[?2026h[39m[49m[59m[Om[?2511?20261[?2026h[39m[49m[59m[Om[?251[?20269[?2026h[39m[49m[59mLOm[?2511?202611?2
26h[39m[49m[59m[Om[?2511?2026[[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?2511?20261[?2026h[39m[49m[59mLOm[?251[?20261[?2026h[39m[49m[59m[om[?
51[?20266[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20260[?2026h[39m[49m[59m[Om[?251[?202611?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39mL
9m[59m[Om[?251[?20262[?2026h[39m[49m[59m[Om[?251[?202611?2026h[39m[49m[59m[Om[?251[?2026m[?2026h[39m[49m[59m[Om[?251[?202611?2026h[39m[49m[59m[Om[?2511?2026?[
[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?202611?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[O
[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[39m[49m[59m[Om[?251[?20261[?2026h[3
...

Minimal reproducer

Running :!yazi inside gvim --clean -u NONE with Yazi 26.1.22 (4e0acf8 2026-01-22) in Ubuntu 22.04

Anything else?

Works fine in Gvim in Windows or in Vim in any other terminal. Affirmed with today's musl build sha256:23499aef713ec226f332c01eecd36c43a925baf82914829ba26ca3b0484dc3f1

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)

[github-actions]

Hey @Konfekt, thank you for opening the issue to help improve Yazi, appreciate it!

I noticed that you did not correctly follow the issue template. Please ensure that:

• The bug can still be reproduced on the newest nightly build.
• The debug information (yazi --debug) is updated for the newest nightly.
• The non-optional items in the checklist are checked.

Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.

Our maintainers work on Yazi in their free time, this helps them work efficiently, understand your setup quickly, and find a more appropriate solution. Thanks for your understanding! 🙏

[Konfekt]

The bug can still be reproduced on the newest nightly build.

Reproduced with today's musl build sha256:23499aef713ec226f332c01eecd36c43a925baf82914829ba26ca3b0484dc3f1

The debug information (yazi --debug) is updated for the newest nightly.

Yazi
    Version  : 26.2.2 (c703332 2026-03-21)
    Debug    : false
    Triple   : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc    : 1.94.0 (4a4ef493 2026-03-02)
    Backtrace: None

Ya
    Version: 26.2.2 (c703332 2026-03-21)

The non-optional items in the checklist are checked.

I am sorry, I thought to have checked as much as I could. What is left?

[sxyazi]

Thanks for the report!

I haven't used gvim myself, a few questions:

• I noticed the terminal in the debug info is ghostty - does gvim use ghostty as its terminal? If not, could you update it to show the output of running yazi --debug from inside gvim?
• Can you upload the logs produced when running yazi in gvim?
• Does this FAQ help resolve the issue?

[Konfekt]

• yazi --debug

Ghostty was an arbitrary secondary choice as :!yazi debug inside Gvim yields that mingled response barely made readbly by OCRing a screenshot

’7?_Gi=31,s=1,v=1,a=q,t=d, f=24; AAAA?\?[>q?[16t?]11;??[0c?8?[38;5;9m? [1m
terminal response timeout: ?[Om?[OmThe request sent by Yazi didn't receive a correct
response.
Please check your terminal environment as per: https://yazi-rs.github.io/docs/faq#tr
B
’[?1049h?P$q q?\?[?12$p?[?u?[0c?[?2004h?[?1004h?[?1000h?[?1002h?[?1003h?[?1015h?[?10
)6h? [38;5;9m? [1m
ferminal response timeout: ?[Om?[OmThe request sent by Yazi didn't receive a correct
response. Please check your terminal environment as per: https://yazi-rs.github.io/docs/faq#tr
B
’]O;yazi - ~/?[?251?[23?[39m?[49m?[59m?[0m?]0;yazi - ~/debug?[?2026h?[39m?[49m?[59m?
(Om? [?251?[?20261?]0;yazi ?[?2026h? [39m? [49m? [59m? [Om? [?251?[?20261[?2026h [39m [49m[59m[Om[?251[?29261[72026h [39m [49m [59m[@m[?251[?2026m?

Thank you for the hint

!env YAZI_LOG=debug yazi

showing

  2026-03-24T16:07:27.861532Z ERROR yazi_adapter::emulator: Terminal failed to respond to DA1 in 1.024069241s: [], error: Kind(TimedOut)
    at yazi-adapter/src/emulator.rs:132

  2026-03-24T16:07:27.864542Z  WARN yazi_adapter::emulator: Failed to detect background color: ""
    at yazi-adapter/src/emulator.rs:202

  2026-03-24T16:07:27.869870Z DEBUG yazi_dds::client: Started new DDS server on instance 1774368447868110
    at yazi-dds/src/client.rs:179

  2026-03-24T16:07:27.870002Z DEBUG yazi_dds::client: Connected to existing DDS server on instance 1774368447868110
    at yazi-dds/src/client.rs:170

  2026-03-24T16:07:28.894270Z ERROR yazi_adapter::emulator: Terminal failed to respond to DA1 in 1.025015162s: [], error: Kind(TimedOut)
    at yazi-adapter/src/emulator.rs:132

  2026-03-24T16:07:28.894901Z ERROR yazi_fs::mounts::linux: Cannot read /dev/disk/by-label
    at yazi-fs/src/mounts/linux.rs:147

  2026-03-24T16:07:28.895147Z ERROR yazi_fs::mounts::linux: Cannot read /dev/disk/by-label
    at yazi-fs/src/mounts/linux.rs:147

which seem indeed to correspond to https://yazi-rs.github.io/docs/faq/#trt

[sxyazi]

Thanks for the update!

From the logs, gvim didn't properly respond to the DA1 request Yazi sent, in that case, you'll need to check and fix your terminal environment to make sure it's DEC VT100-compatible. Closing as I don't think it's a bug in Yazi itself.

[Konfekt]

The G in Gvim stands for GUI. There's no terminal to choose from or to set up.
Passing --clean -u NONE avoids any custom setup while 9.2.140 was the latest build at time of writing.
For short, fixing the terminal environment implies a bug in Linux Gvim itself under Ubuntu 22.04?

[sxyazi]

That could be the case. Yazi is a terminal app and needs a real TTY to run, but it looks like gvim's :! isn't a real TTY.

From https://vi.stackexchange.com/questions/2455/what-additional-features-do-gvim-and-or-macvim-offer-compared-to-vim-inside-a-te:

The :! ex command in gVim doesn't offer a (full) terminal emulator, so starting external programs that use a lot of terminal features won't work very well. For example try using :!vim, :!mutt, or :!irssi from gVim, or pressing K over a word (which, by default, opens the manpage for that word). Also see this.

I'd suggest asking gvim to fix its DA1, or just don't run Yazi inside gvim.