Skip to content
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

Don't activly search for window systems outside the current env #379

Closed
Ongy opened this issue Jan 7, 2018 · 1 comment
Closed

Don't activly search for window systems outside the current env #379

Ongy opened this issue Jan 7, 2018 · 1 comment

Comments

@Ongy
Copy link

Ongy commented Jan 7, 2018

While it makes sense to prefer wayland over X, applications should not try to find wayland compositors that are not pointed to by the env, this messes with multiple session setups.

E.g. when I start alacritty on my X session and have a nested wayland compositor open, it always spawns IN the nested compositor, so I can't get it up on the main session, since it does not respect env.

@Ongy
Copy link
Author

Ongy commented Jan 7, 2018

Ok, apparently this is the default behaviour of libwayland. sorry

https://cgit.freedesktop.org/wayland/wayland/tree/src/wayland-client.c#n864

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant