Allow setting activation_token in supported portals #219
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
apricotbucket28
force-pushed
the
activation-token
branch
from
a014b0e
to
229d250
Compare
apricotbucket28
changed the title
apricotbucket28
force-pushed
the
activation-token
branch
from
229d250
to
cf99f85
Compare
apricotbucket28
force-pushed
the
activation-token
branch
from
764e0b1
to
c28eb4d
Compare
|
Thanks a lot! |
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.
Allow manually setting the
activation_tokenoption for the OpenURI and DynamicLauncher.Launch portals.I saw that #70 is opened but it also includes additional integration, while this just allows setting the token if we already got it from somewhere else (e.g. directly via the Wayland protocol)
(related commit: apricotbucket28/zed@15489a0)