Is there a way to reload the .XCompose file in Fedora?
Clash Royale CLAN TAG#URR8PPP
I am currently custumizing my .XCompose file in Fedora 29 Workstation (with the default GNOME 3, Wayland, etc). It seems that it does follow the rules I add to the ~/.XCompose file, but if I make changes to it then they are only noticed after I log out and log back in again. Is there something I can do to make the changes take effect immediately?
I tried running ibus restart on the terminal but it didn't seem to work. Actually, doing that broke the compose-key functionality completely and I had to restart the session again to fix it.
fedora gnome3 compose-key ibus
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
add a comment |
I am currently custumizing my .XCompose file in Fedora 29 Workstation (with the default GNOME 3, Wayland, etc). It seems that it does follow the rules I add to the ~/.XCompose file, but if I make changes to it then they are only noticed after I log out and log back in again. Is there something I can do to make the changes take effect immediately?
I tried running ibus restart on the terminal but it didn't seem to work. Actually, doing that broke the compose-key functionality completely and I had to restart the session again to fix it.
fedora gnome3 compose-key ibus
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
add a comment |
I am currently custumizing my .XCompose file in Fedora 29 Workstation (with the default GNOME 3, Wayland, etc). It seems that it does follow the rules I add to the ~/.XCompose file, but if I make changes to it then they are only noticed after I log out and log back in again. Is there something I can do to make the changes take effect immediately?
I tried running ibus restart on the terminal but it didn't seem to work. Actually, doing that broke the compose-key functionality completely and I had to restart the session again to fix it.
fedora gnome3 compose-key ibus
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
I am currently custumizing my .XCompose file in Fedora 29 Workstation (with the default GNOME 3, Wayland, etc). It seems that it does follow the rules I add to the ~/.XCompose file, but if I make changes to it then they are only noticed after I log out and log back in again. Is there something I can do to make the changes take effect immediately?
I tried running ibus restart on the terminal but it didn't seem to work. Actually, doing that broke the compose-key functionality completely and I had to restart the session again to fix it.
fedora gnome3 compose-key ibus
fedora gnome3 compose-key ibus
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
edited Dec 22 '18 at 11:45
Rui F Ribeiro
39.1k1479130
39.1k1479130
asked Dec 22 '18 at 0:46
hugomg
1,84231634
asked Dec 22 '18 at 0:46
hugomg
1,84231634
asked Dec 22 '18 at 0:46
hugomg
1,84231634
1,84231634
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
About ~/.XCompose:
This file is read by libX11 whenever a new X program is started. So, your existing terminals won't be able to type these new characters, but any new terminals you launch will.
So, there's no way, unfortunately.
answered Dec 22 '18 at 14:24
Woland
111
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490425%2fis-there-a-way-to-reload-the-xcompose-file-in-fedora%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
About ~/.XCompose:
This file is read by libX11 whenever a new X program is started. So, your existing terminals won't be able to type these new characters, but any new terminals you launch will.
So, there's no way, unfortunately.
answered Dec 22 '18 at 14:24
Woland
111
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
add a comment |
About ~/.XCompose:
This file is read by libX11 whenever a new X program is started. So, your existing terminals won't be able to type these new characters, but any new terminals you launch will.
So, there's no way, unfortunately.
answered Dec 22 '18 at 14:24
Woland
111
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
add a comment |
About ~/.XCompose:
This file is read by libX11 whenever a new X program is started. So, your existing terminals won't be able to type these new characters, but any new terminals you launch will.
So, there's no way, unfortunately.
answered Dec 22 '18 at 14:24
Woland
111
About ~/.XCompose:
This file is read by libX11 whenever a new X program is started. So, your existing terminals won't be able to type these new characters, but any new terminals you launch will.
So, there's no way, unfortunately.
answered Dec 22 '18 at 14:24
Woland
111
answered Dec 22 '18 at 14:24
Woland
111
answered Dec 22 '18 at 14:24
Woland
111
answered Dec 22 '18 at 14:24
Woland
111
111
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
add a comment |
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
This isn't the same behavior I am encountering though. I have to restart the whole desktop session. Even relaunching programs is not enough.
– hugomg
Dec 22 '18 at 16:11
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490425%2fis-there-a-way-to-reload-the-xcompose-file-in-fedora%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown