zellij icon indicating copy to clipboard operation
zellij copied to clipboard

Published 20 hours ago • verified publisher icon zellij-org

Hang when using any keybind

Open crides opened this issue 1 year ago • 4 comments

Thank you for taking the time to file this issue! Please follow the instructions and fill in the missing parts below the instructions, if it is meaningful. Try to be brief and concise.

In Case of Graphical or Performance Issues

  1. Delete the contents of /tmp/zellij-1000/zellij-log, ie with cd /tmp/zellij-1000/ and rm -fr zellij-log/
  2. Run zellij --debug
  3. Run stty size, copy the result and attach it in the bug report
  4. Recreate your issue.
  5. Quit Zellij immediately with ctrl-q (your bug should ideally still be visible on screen)

Please attach the files that were created in /tmp/zellij-1000/zellij-log/ to the extent you are comfortable with.

Basic information

zellij --version: 0.31.4 (from Arch) stty size: 31 172 uname -av or ver(Windows): Linux Aostro-5468 5.16.15-arch1-1 #1 SMP PREEMPT Thu, 17 Mar 2022 00:30:09 +0000 x86_64 GNU/Linux

List of programs you interact with as, PROGRAM --version: output cropped meaningful, for example: alacritty --version: alacritty 0.8.0-dev (3ed0430) (ligature fork)

Further information

To reproduce, I start a new terminal window, start zellij, and press any of the keybinds listed (other than ctrl-q), then zellij immediately hangs (see below). No logs are produced after the hang. It doesn't seem to respond to any keys.

Config is generated from zellij setup --dump-config, with only theme changed to gruvbox-dark (somehow this is not reflected in the UI even though zellij setup --check does point to the correct config)

maim-2022 09 18 14 45 07

crides avatar Sep 18 '22 19:09 crides

So apparently vim's = messed up the structure of the config file, but neither zellij setup --check or the executable itself reported the problem until when the actual keybinds are used. So I'll still consider this as a bug, but now the problem is much clearer

(I also figured out why the themes didn't work; if there are builtin plugins should there also be builtin themes?)

crides avatar Sep 18 '22 20:09 crides

@crides - could you explain a little what you mean by vim's = messing up the config file structure?

imsnif avatar Sep 19 '22 07:09 imsnif

Sorry I should've explained. = in vim is the auto indent operator, and it turns out that it doesn't maintain the structure of the file

crides avatar Sep 19 '22 14:09 crides

Ah yeah, the troubles of YAML :/ This will be solved very soon when we move to KDL

imsnif avatar Sep 19 '22 14:09 imsnif