-
Notifications
You must be signed in to change notification settings - Fork 38
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
Custom Compose key sequences don't work in Signal #259
Comments
Which other Flatpak apps allow this feature so that we can adapt it here? |
I'm not sure which other apps do this, but running the following command fixed my issue: flatpak override org.signal.Signal --filesystem=/home/csha/.XCompose |
I have the same issue and √ ; bat /var/lib/flatpak/overrides/org.signal.Signal
───────┬────────────────────────────────────────────────────────────────────────
│ File: /var/lib/flatpak/overrides/org.signal.Signal
───────┼────────────────────────────────────────────────────────────────────────
1 │ [Context]
2 │ filesystems=home;/home/user/.XCompose;
───────┴──────────────────────────────────────────────────────────────────────── |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use Compose key with custom sequences defined in
~/XCompose
. I can use these sequences in all apps (even Flatpak ones) except for Signal. In Signal, compose key works, but only the default predefined sequences are available.As a walkaround, I have to switch to a different app, type the symbols I need, copy them, switch back to Signal, and paste. Doing this several times a day gets a bit annoying, so if there was a way to resolve this, I'd love it.
The text was updated successfully, but these errors were encountered: