You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use Quake-Terminal extension in X11, for some reason it simply does not work. What happens is very uniquely unusual in what does actually happen though.
With kitty, or alacritty, no configuration or with configuration, does not matter, if kitty or alacritty is used as the Terminal Application starts a terminal, it runs the terminal, but does not properly show the terminal at all. Instead where the terminal should be, there's "dead space" that visually can be seen when it's opening, closing, or there's moving content in the area of which is in that "terminal area". I will get a visual recording of this for demonstration as well.
This seems to only happen on at least these GPU-enhanced terminals like kitty and alacritty, so far in my testing of this, and only in X11 specifically, On wayland, I've seen no apparent issue.
The text was updated successfully, but these errors were encountered:
https://0x0.st/XcZR.mov
There's the effect of the issue I'm seeing.
Now, to note, this problem does not occur if I run kitty or alacritty prior to using the keybinding shortcut. It's basically when the extension itself loads it that it becomes an issue.
Happens to me aswell. Using ubuntu 24.04 on XORG. On Wayland works just fine. Launching it before using the shortcut avoid this issue, so I swear its something on how extension launch the terminal.
When I use Quake-Terminal extension in X11, for some reason it simply does not work. What happens is very uniquely unusual in what does actually happen though.
With kitty, or alacritty, no configuration or with configuration, does not matter, if kitty or alacritty is used as the Terminal Application starts a terminal, it runs the terminal, but does not properly show the terminal at all. Instead where the terminal should be, there's "dead space" that visually can be seen when it's opening, closing, or there's moving content in the area of which is in that "terminal area". I will get a visual recording of this for demonstration as well.
This seems to only happen on at least these GPU-enhanced terminals like kitty and alacritty, so far in my testing of this, and only in X11 specifically, On wayland, I've seen no apparent issue.
The text was updated successfully, but these errors were encountered: