How to set compose key on Centos 7 server
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
While working on Centos 7 servers and editing files (usually via vim), I'd like to type umlauts, accent marks, etc. How do I define a compose key for this? (Or is one already set by default?) I see similar questions and answers for various desktops, but am looking for the steps to enable this on servers.
centos
add a comment |Â
up vote
0
down vote
favorite
While working on Centos 7 servers and editing files (usually via vim), I'd like to type umlauts, accent marks, etc. How do I define a compose key for this? (Or is one already set by default?) I see similar questions and answers for various desktops, but am looking for the steps to enable this on servers.
centos
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
While working on Centos 7 servers and editing files (usually via vim), I'd like to type umlauts, accent marks, etc. How do I define a compose key for this? (Or is one already set by default?) I see similar questions and answers for various desktops, but am looking for the steps to enable this on servers.
centos
While working on Centos 7 servers and editing files (usually via vim), I'd like to type umlauts, accent marks, etc. How do I define a compose key for this? (Or is one already set by default?) I see similar questions and answers for various desktops, but am looking for the steps to enable this on servers.
centos
asked Mar 7 at 1:25
Anatortoise House
1032
1032
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54
add a comment |Â
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
You have to set up the compose key on your client, not the server.
It seems to work similarly to modifier keys (e.g. shift). The client doesn't send shift itself to the server, just the final (modified) glyph.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You have to set up the compose key on your client, not the server.
It seems to work similarly to modifier keys (e.g. shift). The client doesn't send shift itself to the server, just the final (modified) glyph.
add a comment |Â
up vote
1
down vote
accepted
You have to set up the compose key on your client, not the server.
It seems to work similarly to modifier keys (e.g. shift). The client doesn't send shift itself to the server, just the final (modified) glyph.
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You have to set up the compose key on your client, not the server.
It seems to work similarly to modifier keys (e.g. shift). The client doesn't send shift itself to the server, just the final (modified) glyph.
You have to set up the compose key on your client, not the server.
It seems to work similarly to modifier keys (e.g. shift). The client doesn't send shift itself to the server, just the final (modified) glyph.
answered Mar 8 at 5:57
Sparhawk
8,33363487
8,33363487
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428655%2fhow-to-set-compose-key-on-centos-7-server%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Thanks, that's what I get for using an unfamiliar client machine! Yes, as you say, the character encoding is getting 'composed' on the client side before being sent over the network, rather than being composed on the server side.
â Anatortoise House
Mar 8 at 5:54