Kitty graphics protocol emitted into window

[CT075]

Hello,

I Installed lean.nvim through lazy and it's mostly been great! However, I've noticed some strange rendering issues:

Notice the ANSI escape codes (at least, they look like ANSI codes) in the top left and middle right, and the fact that the later code isn't highlighted properly.

These artifacts show up inconsistently, but they do go away on a manual screen refresh (<C-L>). I'm not sure what might be causing this (maybe my terminal multiplexer? I'm using Zellij on ITerm2), but any advice would be appreciated.

Thanks!

[Julian]

This'll be our kitty graphics protocol detection misbehaving under your precise terminal setup. I'll have to see if I can figure out what needs twealing given I'm on a different one

[CT075]

It's almost certainly Zellij's fault; supporting the Kitty protocol is a longstanding issue.

That said, I'm seeing these artifacts even with graphics = {enabled=false}. Am I configuring things wrong? I'm currently invoking lean.nvim via

require("lean").setup { mappings = true, graphics = { enabled = false } }

and lua =require'lean.config'().graphics.enabled gives false as expected.

EDIT: For that matter, lua =require'kitty'.available() also gives false.

[Julian]

Hey! Can you give 651b6ea a shot and let me know if that helps? It should at least allow you to disable explicitly now.

[Julian]

Closing as hopefully this did it but feel free to let me know if not!

[CT075]

Hey, sorry for missing this! It seems to work great!

[CT075]

@Julian

Looks like I spoke too soon:

They're definitely much less frequent than they used to be, but I'd expect the graphics to be disabled entirely (I have graphics.enabled = false as before). Notably, vim.env.ZELLIJ appears to be false, but maybe that's due to my own misconfiguration.

I suspect this actually has nothing to do with Zellij or Kitty after all; these don't look like Kitty codes, nor does the issue go away on a stock Iterm2 with no multiplexer. I'm wondering if there might be something weird going on between nvim and iterm that lean.nvim just happens to exercise poorly. The main reason that I believe this to be Lean.nvim specific is that I cannot cause the issue to occur with any non-Lean file or buffer.