-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
force kitty so use xwayland as backend #2648
Comments
https://sw.kovidgoyal.net/kitty/conf.html#opt-kitty.linux_display_server might be what you want. |
Did you try this? It does exist. From the changelog:
|
thanks! yeah. this dont seem to work here. |
Try |
nice. this is new info to me :-) |
nope. no cigar. :-) |
Like so: kitty -o linux_display_server=x11 |
yes. niice. this works indeed. I will go and check the |
Glad it works now. |
System: Arch linux, Sway wm
I am normally not in the need of opening kitty in X under Wayland. But for sharing the kitty window during jitsu meet or other conference platform sessions it is needed.
When unsetting the wayland display
unset WAYLAND_DISPLAY
apps then try to open with XWayland. This works with some native Wayland terminal emulators and other native Wayland apps.But with kitty, i guess after the KITTY_ENABLE_WAYLAND env var is longer needed , I cant seem to figure out how to force/make kitty to open with X.
unset WAYLAND_DISPLAY && kitty
stills opens a kitty with Wayland. not X.So i tried exporting it to an empty string. (which also works with other wayland native apps)
export WAYLAND_DISPLAY="" && kitty
here i found kitty throwing an GLFW error.It seems kitty still wants to open with wayland.
Is there an env var like
KITTY_DISABLE_WAYLAND
or maybeKITTY_FORCE_UNSECURE_X
:=) and thanks for making this wonderful terminal emulator.
The text was updated successfully, but these errors were encountered: