Closed svenihoney closed 4 months ago
Does not reproduce for me with
kitty --config=NONE -o 'map kitty_mod+n new_os_window_with_cwd' -1
1) Press ctrl_shift_n 2) In the new window press ctrl_shift+t 3) observe a second tab opening with the tab bar, as expected.
Okay, interesting. I can reproduce the behavior on my system, and instead of trying to find out what the root cause of the problem is (maybe my environment, font, wayland, used shell or whatever) you simply close the issue because it is working in YOUR environment? Never seen something like this.
Surely I would have been willing to help to find the error.
I think I will look for a different terminal if this is your idea of community support.
Because this is very clearly an issue specific to your environment, If I had to guess it would be something related to using nix, which tends to break software in weird and wonderful ways. I am not your personal support staff. As stated in https://github.com/kovidgoyal/kitty/blob/master/CONTRIBUTING.md#reporting-bugs bug reports that I dont feel are actual bugs in kitty are closed. Closed status doesn't mean I will not respond further. You are welcome to provide further information that might help track down the cause or ask for guidance in debugging it, but with the information you have so far provided I dont see how this can possibly be a bug in kitty.
If you want to debug further, I suggest you start with running with --debug-input which will tell you if the key press triggered the shortcut or not. Also try using the official kitty binaries instead of the nix package.
I'm also experiencing this issue on Arch + Hyprland. It started to happen on 0.34.0
for me, 0.33.1
had no issue. I did a git bisect
between master
and 0.33.1
running kitty with:
./kitty/launcher/kitty --config=NONE -o 'map kitty_mod+n new_os_window_with_cwd' -o 'map kitty_mod+t new_tab_with_cwd' -1
And opening a couple tabs in the first window, it always works fine. Then I open a new window and try to open a couple tabs in it, that's when issue starts to appear. The tabs are there, but tab bar is not visible.
First bad commits seems to be https://github.com/kovidgoyal/kitty/commit/a40a36d191285185e99f3699f314aca504ca0a75
I observed a couple behaviors.
Just some kind of an artifact.
Sometimes seems like it kind of wraps around. Instead of tab bar it shows the topmost line from the normal output:
Other times the place where tab bar should be is just transparent. And it blinks between transparent and terminal background together with cursor blinking.
What else can I do to help debugging this?
kitty 0.33.1 (a40a36d191) created by Kovid Goyal
Linux phoenix 6.9.2-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sun, 26 May 2024 01:30:09 +0000 x86_64
Arch Linux 6.9.2-zen1-1-zen (/dev/tty)
Running under: Wayland (Hyprland v0.40.0,)
Frozen: False
Paths:
kitty: /home/faergeek/projects/kitty/kitty/launcher/kitty
base dir: /home/faergeek/projects/kitty
extensions dir: /home/faergeek/projects/kitty/kitty
system shell: /usr/bin/fish
Loaded config overrides:
map kitty_mod+n new_os_window_with_cwd
map kitty_mod+t new_tab_with_cwd
Config options different from defaults:
Changed shortcuts:
kitty_mod+n → new_os_window_with_cwd
kitty_mod+t → new_tab_with_cwd
Important environment variables seen by the kitty process:
PATH /home/faergeek/projects/kitty/kitty/launcher:/home/faergeek/.opam/default/bin:/home/faergeek/.asdf/shims:/home/faergeek/.asdf/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
LANG ru_RU.UTF-8
VISUAL nvim
EDITOR nvim
SHELL /usr/bin/fish
DISPLAY :0
WAYLAND_DISPLAY wayland-1
USER faergeek
XDG_SESSION_TYPE wayland
XDG_DATA_DIRS /home/faergeek/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_BACKEND wayland
XDG_CURRENT_DESKTOP Hyprland
XDG_SESSION_ID 3
XDG_RUNTIME_DIR /run/user/1000
XDG_SEAT seat0
Is it hyprland specific? Does it happen in another wayland compositor? Or under XWayland (linux_display_server x11) in kitty.conf.
Wow, thank was quick! Thank you very much! Confirming that the latest commit fixed the issue for me :+1:
Describe the bug I have mapped the new window command to CTRL+SHIFT+n like this:
If I open a new window with this key combo, a new window is opened correctly. But if I open a new tab, the tab bar display is incorrect.
To Reproduce Steps to reproduce the behavior:
kitty -1
Screenshots Healthy terminal (first instance):
Faulty instance in new window and second tab opened:
Environment details
Additional context Same problem with
kitty --config NONE
and CTRL+SHIFT+N, CTRL+SHIFT+T.