Mixing
How to make the double quote behave as a dead key except when it is used in combination with itself
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
When I use a keyboard, I expect the following behaviours (and I rely on these behaviours):
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should print"
Press ", release ", press ", release ": Should print""
I understand that this behaviour is defined by a keyboard layout, so I did some research.
On keyboard layout "English - US with dead keys", I get the top 2 behaviours that I prefer, but the last behaviour is not fulfilled, and I get the weird character ¨ when I try that.
On keyboard layout "English - US with AltGr dead keys", I only get the last behaviour, but the key doesn't behave dead anymore.
How can I modify the keyboard layout to fulfill the 3 behaviours I expect when I use a keyboard?
keyboard-layout
edited 3 mins ago
jwodder
193210
asked 3 hours ago
Ferrybig
1741213
add a comment |Â
up vote
4
down vote
favorite
When I use a keyboard, I expect the following behaviours (and I rely on these behaviours):
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should print"
Press ", release ", press ", release ": Should print""
I understand that this behaviour is defined by a keyboard layout, so I did some research.
On keyboard layout "English - US with dead keys", I get the top 2 behaviours that I prefer, but the last behaviour is not fulfilled, and I get the weird character ¨ when I try that.
On keyboard layout "English - US with AltGr dead keys", I only get the last behaviour, but the key doesn't behave dead anymore.
How can I modify the keyboard layout to fulfill the 3 behaviours I expect when I use a keyboard?
keyboard-layout
edited 3 mins ago
jwodder
193210
asked 3 hours ago
Ferrybig
1741213
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
When I use a keyboard, I expect the following behaviours (and I rely on these behaviours):
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should print"
Press ", release ", press ", release ": Should print""
I understand that this behaviour is defined by a keyboard layout, so I did some research.
On keyboard layout "English - US with dead keys", I get the top 2 behaviours that I prefer, but the last behaviour is not fulfilled, and I get the weird character ¨ when I try that.
On keyboard layout "English - US with AltGr dead keys", I only get the last behaviour, but the key doesn't behave dead anymore.
How can I modify the keyboard layout to fulfill the 3 behaviours I expect when I use a keyboard?
keyboard-layout
edited 3 mins ago
jwodder
193210
asked 3 hours ago
Ferrybig
1741213
When I use a keyboard, I expect the following behaviours (and I rely on these behaviours):
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should print"
Press ", release ", press ", release ": Should print""
I understand that this behaviour is defined by a keyboard layout, so I did some research.
On keyboard layout "English - US with dead keys", I get the top 2 behaviours that I prefer, but the last behaviour is not fulfilled, and I get the weird character ¨ when I try that.
On keyboard layout "English - US with AltGr dead keys", I only get the last behaviour, but the key doesn't behave dead anymore.
How can I modify the keyboard layout to fulfill the 3 behaviours I expect when I use a keyboard?
keyboard-layout
keyboard-layout
edited 3 mins ago
jwodder
193210
asked 3 hours ago
Ferrybig
1741213
edited 3 mins ago
jwodder
193210
asked 3 hours ago
Ferrybig
1741213
edited 3 mins ago
jwodder
193210
edited 3 mins ago
jwodder
193210
edited 3 mins ago
jwodder
193210
193210
asked 3 hours ago
Ferrybig
1741213
asked 3 hours ago
Ferrybig
1741213
asked 3 hours ago
Ferrybig
1741213
1741213
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
After trying differend ways for this problem, I eventually found a solution with help in chat for this problem
The root cause of the problem is actually caused by the fact that linux does not have an dead_apostrophe and a dead_quotedbl by default, so the default "us dead keyboard layout" have either mapped a dead_acute or a non dead key mapped to ".
This ment this problem is not being fixable by making your own custom keyboard layout, as I was suggested in the chat.
After further research and the just is time learning of new keywords to search, I found this solution on Unix & Linux StackExchange, what helped me solve the problem.
I followed the following steps listed in that answer:
sudo apt install uimecho 'export GTK_IM_MODULE="uim"' >> ~./profileecho 'export QT_IM_MODULE="uim"' >> ~./profilecurl 'https://gist.githubusercontent.com/guiambros/b773ee85746e06454596/raw/0ea6d7f7cf9a6ff38b4cafde24dd43852e46d5e3/.XCompose' > ~/.XCompose- Rebooted Ubuntu
After these steps, I managed to fulfill the following expectations I had about my keyboard:
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should"
Press ", release ", press ", release ": Should print""
answered 1 hour ago
Ferrybig
1741213
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
After trying differend ways for this problem, I eventually found a solution with help in chat for this problem
The root cause of the problem is actually caused by the fact that linux does not have an dead_apostrophe and a dead_quotedbl by default, so the default "us dead keyboard layout" have either mapped a dead_acute or a non dead key mapped to ".
This ment this problem is not being fixable by making your own custom keyboard layout, as I was suggested in the chat.
After further research and the just is time learning of new keywords to search, I found this solution on Unix & Linux StackExchange, what helped me solve the problem.
I followed the following steps listed in that answer:
sudo apt install uimecho 'export GTK_IM_MODULE="uim"' >> ~./profileecho 'export QT_IM_MODULE="uim"' >> ~./profilecurl 'https://gist.githubusercontent.com/guiambros/b773ee85746e06454596/raw/0ea6d7f7cf9a6ff38b4cafde24dd43852e46d5e3/.XCompose' > ~/.XCompose- Rebooted Ubuntu
After these steps, I managed to fulfill the following expectations I had about my keyboard:
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should"
Press ", release ", press ", release ": Should print""
answered 1 hour ago
Ferrybig
1741213
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
add a comment |Â
up vote
3
down vote
After trying differend ways for this problem, I eventually found a solution with help in chat for this problem
The root cause of the problem is actually caused by the fact that linux does not have an dead_apostrophe and a dead_quotedbl by default, so the default "us dead keyboard layout" have either mapped a dead_acute or a non dead key mapped to ".
This ment this problem is not being fixable by making your own custom keyboard layout, as I was suggested in the chat.
After further research and the just is time learning of new keywords to search, I found this solution on Unix & Linux StackExchange, what helped me solve the problem.
I followed the following steps listed in that answer:
sudo apt install uimecho 'export GTK_IM_MODULE="uim"' >> ~./profileecho 'export QT_IM_MODULE="uim"' >> ~./profilecurl 'https://gist.githubusercontent.com/guiambros/b773ee85746e06454596/raw/0ea6d7f7cf9a6ff38b4cafde24dd43852e46d5e3/.XCompose' > ~/.XCompose- Rebooted Ubuntu
After these steps, I managed to fulfill the following expectations I had about my keyboard:
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should"
Press ", release ", press ", release ": Should print""
answered 1 hour ago
Ferrybig
1741213
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
add a comment |Â
up vote
3
down vote
up vote
3
down vote
After trying differend ways for this problem, I eventually found a solution with help in chat for this problem
The root cause of the problem is actually caused by the fact that linux does not have an dead_apostrophe and a dead_quotedbl by default, so the default "us dead keyboard layout" have either mapped a dead_acute or a non dead key mapped to ".
This ment this problem is not being fixable by making your own custom keyboard layout, as I was suggested in the chat.
After further research and the just is time learning of new keywords to search, I found this solution on Unix & Linux StackExchange, what helped me solve the problem.
I followed the following steps listed in that answer:
sudo apt install uimecho 'export GTK_IM_MODULE="uim"' >> ~./profileecho 'export QT_IM_MODULE="uim"' >> ~./profilecurl 'https://gist.githubusercontent.com/guiambros/b773ee85746e06454596/raw/0ea6d7f7cf9a6ff38b4cafde24dd43852e46d5e3/.XCompose' > ~/.XCompose- Rebooted Ubuntu
After these steps, I managed to fulfill the following expectations I had about my keyboard:
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should"
Press ", release ", press ", release ": Should print""
answered 1 hour ago
Ferrybig
1741213
After trying differend ways for this problem, I eventually found a solution with help in chat for this problem
The root cause of the problem is actually caused by the fact that linux does not have an dead_apostrophe and a dead_quotedbl by default, so the default "us dead keyboard layout" have either mapped a dead_acute or a non dead key mapped to ".
This ment this problem is not being fixable by making your own custom keyboard layout, as I was suggested in the chat.
After further research and the just is time learning of new keywords to search, I found this solution on Unix & Linux StackExchange, what helped me solve the problem.
I followed the following steps listed in that answer:
sudo apt install uimecho 'export GTK_IM_MODULE="uim"' >> ~./profileecho 'export QT_IM_MODULE="uim"' >> ~./profilecurl 'https://gist.githubusercontent.com/guiambros/b773ee85746e06454596/raw/0ea6d7f7cf9a6ff38b4cafde24dd43852e46d5e3/.XCompose' > ~/.XCompose- Rebooted Ubuntu
After these steps, I managed to fulfill the following expectations I had about my keyboard:
Press ", release ": Should remember the key as a dead key
Press ", release ", press <space>, release <space>: Should"
Press ", release ", press ", release ": Should print""
answered 1 hour ago
Ferrybig
1741213
answered 1 hour ago
Ferrybig
1741213
answered 1 hour ago
Ferrybig
1741213
answered 1 hour ago
Ferrybig
1741213
1741213
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
add a comment |Â
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
To log out of the session and log back in should be enough to let the changes take effect. No need to reboot.
– David Foerster
24 secs ago
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%2faskubuntu.com%2fquestions%2f1077736%2fhow-to-make-the-double-quote-behave-as-a-dead-key-except-when-it-is-used-in-comb%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