xmodmap key bindings reset when I open a new tab in the shell
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
When I open a shell in ranger with shift-s, open vim and then open a shell with :sh or open a new shell tab with ctrl-shift-t, my xmodmap keybindings (swapped caps lock and escape keys) are reset. This is what the terminal spits out:
xmodmap: please release the following keys within 2 seconds:
t (keysym 0x74, keycode 28)
Shift_R (keysym 0xffe2, keycode 62)
My keybindings are very important to me as I am an active vim user currently working with Typescript (I need quick access to the shell to compile my code). I set my keybindings with xmodmap ~/.Xmodmap
(the .Xmodmap file contains my xmodmap commands) and I added that command to my .bashrc.
For some more context I am using Ubuntu 16.4 and I recently created a ranger configuration file (~/.config/ranger/rifle.conf) to add support for the .ts file extension. I not an expert ranger or bash user, but both are very important for my workflow. Help would be greatly appreciated.
edit: this problem is solved when I remove xmodmap ~/.Xmodmap
from my .bashrc, but now I have no way of having my xmodmap keybindings enabled on startup. Adding @reboot xmodmap ~/.Xmodmap
to my crontab file does not work (maybe I should post a separate question for that, but I'll leave this question here for future reference).
bash vim bashrc xmodmap ranger
add a comment |Â
up vote
2
down vote
favorite
When I open a shell in ranger with shift-s, open vim and then open a shell with :sh or open a new shell tab with ctrl-shift-t, my xmodmap keybindings (swapped caps lock and escape keys) are reset. This is what the terminal spits out:
xmodmap: please release the following keys within 2 seconds:
t (keysym 0x74, keycode 28)
Shift_R (keysym 0xffe2, keycode 62)
My keybindings are very important to me as I am an active vim user currently working with Typescript (I need quick access to the shell to compile my code). I set my keybindings with xmodmap ~/.Xmodmap
(the .Xmodmap file contains my xmodmap commands) and I added that command to my .bashrc.
For some more context I am using Ubuntu 16.4 and I recently created a ranger configuration file (~/.config/ranger/rifle.conf) to add support for the .ts file extension. I not an expert ranger or bash user, but both are very important for my workflow. Help would be greatly appreciated.
edit: this problem is solved when I remove xmodmap ~/.Xmodmap
from my .bashrc, but now I have no way of having my xmodmap keybindings enabled on startup. Adding @reboot xmodmap ~/.Xmodmap
to my crontab file does not work (maybe I should post a separate question for that, but I'll leave this question here for future reference).
bash vim bashrc xmodmap ranger
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
When I open a shell in ranger with shift-s, open vim and then open a shell with :sh or open a new shell tab with ctrl-shift-t, my xmodmap keybindings (swapped caps lock and escape keys) are reset. This is what the terminal spits out:
xmodmap: please release the following keys within 2 seconds:
t (keysym 0x74, keycode 28)
Shift_R (keysym 0xffe2, keycode 62)
My keybindings are very important to me as I am an active vim user currently working with Typescript (I need quick access to the shell to compile my code). I set my keybindings with xmodmap ~/.Xmodmap
(the .Xmodmap file contains my xmodmap commands) and I added that command to my .bashrc.
For some more context I am using Ubuntu 16.4 and I recently created a ranger configuration file (~/.config/ranger/rifle.conf) to add support for the .ts file extension. I not an expert ranger or bash user, but both are very important for my workflow. Help would be greatly appreciated.
edit: this problem is solved when I remove xmodmap ~/.Xmodmap
from my .bashrc, but now I have no way of having my xmodmap keybindings enabled on startup. Adding @reboot xmodmap ~/.Xmodmap
to my crontab file does not work (maybe I should post a separate question for that, but I'll leave this question here for future reference).
bash vim bashrc xmodmap ranger
When I open a shell in ranger with shift-s, open vim and then open a shell with :sh or open a new shell tab with ctrl-shift-t, my xmodmap keybindings (swapped caps lock and escape keys) are reset. This is what the terminal spits out:
xmodmap: please release the following keys within 2 seconds:
t (keysym 0x74, keycode 28)
Shift_R (keysym 0xffe2, keycode 62)
My keybindings are very important to me as I am an active vim user currently working with Typescript (I need quick access to the shell to compile my code). I set my keybindings with xmodmap ~/.Xmodmap
(the .Xmodmap file contains my xmodmap commands) and I added that command to my .bashrc.
For some more context I am using Ubuntu 16.4 and I recently created a ranger configuration file (~/.config/ranger/rifle.conf) to add support for the .ts file extension. I not an expert ranger or bash user, but both are very important for my workflow. Help would be greatly appreciated.
edit: this problem is solved when I remove xmodmap ~/.Xmodmap
from my .bashrc, but now I have no way of having my xmodmap keybindings enabled on startup. Adding @reboot xmodmap ~/.Xmodmap
to my crontab file does not work (maybe I should post a separate question for that, but I'll leave this question here for future reference).
bash vim bashrc xmodmap ranger
edited Jun 21 at 17:26
asked Jun 20 at 20:40
Liam Thornback
112
112
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f450971%2fxmodmap-key-bindings-reset-when-i-open-a-new-tab-in-the-shell%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