Add a feature to enable Wayland support #2562
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also lapce/floem#93
This makes it possible to test Glazier's native Wayland support in Lapce, without force-enabling it for all users, as it isn't yet ready. This still hangs for me (in release mode), but it appears to mostly work in debug mode. I believe this hang is still the one tracked in Smithay/calloop#127
I'm not sure why it fails in release despite working in debug mode - I guess it must be a race condition due to Lapce's multi-threading. Anyway, that's less important to debug
CHANGELOG.mdif this change could be valuable to users